agent traffic
Sample dataDocs

Agent paths

The sequences agents take through your API, and which ones end in an error.

Agent pathsSessions are grouped by session hint, or else by account ID. Events with neither are unattributed: grouping by IP is not done, because agents share cloud IPs and different agents would merge. 125 events in this range are unattributed (no session hint or account ID) and are not in any path.

Top 5 of 8 paths from 123 sessions in the last 14 days.

  1. 33 sessions26.8%
    docs_view
    api_key_created
    api_callFailed: 401 Unauthorized: X-Api-Key header is not accepted, send Authorization: Bearer
  2. 23 sessions18.7%
    docs_view
    sdk_install
    api_callOK
  3. 22 sessions17.9%
    docs_view
    meter_createFailed: 422 Unprocessable: event_name is required
  4. 13 sessions10.6%
    docs_viewNo status
  5. 12 sessions9.8%
    docs_view
    api_call_401Failed: 401 Unauthorized (guessed)

Failed sessions, one per error

The latest session each Fix next error ended, event by event. Times are from the session's first event.

401 Unauthorized: X-Api-Key header is not accepted, send Authorization: Bearer

Intent api_key_created · agent python-httpx · started 2026-10-22 17:56 UTC

  1. 00:00docs_view
  2. 00:45api_key_created
  3. 01:50api_call401 Unauthorized: X-Api-Key header is not accepted, send Authorization: Bearer
  4. Session ended

Open session

422 Unprocessable: event_name is required

Intent meter_create · agent perplexity.ai · started 2026-10-22 15:49 UTC

  1. 00:00docs_view
  2. 00:25meter_create422 Unprocessable: event_name is required
  3. Session ended

Open session

401 Unauthorized (guessed)

Intent api_call_401 · agent perplexity.ai · started 2026-10-22 05:14 UTC

  1. 00:00docs_view
  2. 01:25api_call_401401 Unauthorized
  3. Session ended

Open session

About these numbers