Usage event
Looks up one request by the X-Request-Id header its response
carried. Returns every field of an event in GET /account/usage/events
plus what was sent:
request: the body, query parameters and path parameters.headers: the request headers, withauthorizationandapikeyshown as<redacted>.response: the error body a failed request got back, redacted. It is JSON when the body was JSON, and a string when it was not or was cut at 32 KB. It isnullon a success and on a429.
A request id that belongs to another team returns 404, the same as
one that never existed.
This endpoint is free: the response carries no X-Credits-Used
header. It shares a limit of 60 requests per minute with the other
/account/usage/* endpoints.
Authorizations
Headers
Path Parameters
Response
The event, with the stored request.
An event plus the request that was stored for it.
The client detected from the request, for example python, node, curl or claude-code. It comes from the MCP client tag, the CLI's user agent, or a category based on your User-Agent header. New values can appear at any time. Empty for batch jobs, watches and exports, and usually for requests refused with a 429.
"curl"

