Skip to main content

Investigate a request

Use Usage for request-level observability and Billing for account funding and balance movements. SDK token counts help interpret a response; the recorded Usage charge is the billing reference.

Keep a safe correlation record​

When available, preserve the response's X-Primex-Request-ID, the UTC submission time, offering ID, application operation ID, HTTP status and safe error code. Keep your own correlation ID too so you can locate a timeout that produced no response headers. Avoid storing API keys, upload URLs, full prompts or file contents in ordinary logs. A request ID does not authorize access to another account's data.

Find the request​

  1. Open Usage in the owning account.
  2. Set a period that includes submission. Available periods are 24 hours, 7 days, 30 days, UTC month to date, and all recorded history.
  3. Filter by offering, API key, source, service or outcome to narrow the list. Submit a search when needed; changing a draft search alone does not apply it.
  4. Open the request and compare its recorded identifier with your correlation record.

Applied filters affect the summary, trend, breakdown and history together. Sort and page affect the history only. All-history totals cover recorded history; its chart groups by UTC month rather than pretending to be a real-time feed.

Read the outcome and charge​

A request can have multiple recorded components, such as model tokens and a provider-run search. Compare the net charge with its charge/refund components. Keep input/output/cache buckets and service units distinct; do not add pages and tokens into one usage quantity or recompute an old charge at current prices.

The details identify the offering, key, source, outcome, recorded timing, Requested route, and Routing tier. The served tier is distinct from the requested mode and the model's creator. Concrete upstream routes, supplier credentials and private request bodies are not exposed in customer Usage. Time to first token is not persisted as a request metric; do not infer it from another duration field.

A 200 can precede a stream error. A local timeout after dispatch can hide a completed operation. Use the recorded result and partial/uncertain outcome rules before sending another paid request. Multi-stage recipes have independent request records: a later failed translation does not undo an earlier completed transcription.

Escalate a discrepancy​

Contact Support with the Primex request ID, UTC time, offering, expected result and safe error details. For media, include the operation ID you retained before submission. Describe which recorded charge or outcome needs review; do not send credentials or private input to establish it.

See Billing for meters, funding, reservations and corrections, Production for deployment controls, and API Keys for attribution and spending caps.