API and Network
Capture direct requests, assertions, waterfall evidence, and HAR exports.
User journeys often pass in the browser while failing in the system behind it. Autonomy records network activity and can run direct API checks so evidence includes both what the user saw and what the backend returned.
Direct checks
Use direct API checks for state that is expensive or unreliable to verify through UI alone. Keep the user-visible journey in the plan, then add API assertions for totals, webhooks, entitlements, records, and backend side effects.
/api/orders/:id1{2 "status": "paid",3 "currency": "USD"4}Waterfall evidence
Autonomy records request timing, status codes, selected headers, and assertion results. When a failure depends on redirects, blocked requests, or slow third-party calls, export HAR and share it with the team that owns the integration.
Common uses
- Confirm checkout created the right order and entitlement.
- Verify a webhook changed state after a browser action.
- Check that a protected endpoint rejects unauthorized access.
- Compare API totals with what the UI displays.
- Capture request failures that only appear in preview or staging.
Review pattern
Start with the user-visible failure. If the UI state is ambiguous, open the network evidence and direct check output for the same step. A good report should point to the request or assertion that proves the underlying state.