Usage
Usage & cost accounting
Every response carries what it cost. usage.cost is the exact amount charged in USD — the same number written to your invoice — so you can attribute spend per request without reconciling anything.
| Field | What it is |
|---|---|
usage.cost | What this request charged, in USD |
usage.cost_details | The same amount split by axis (input, output, cache, image…), plus currency and any discount that applied |
usage.is_byok | Always false: Oxyy serves every request on its own provider keys |
X-Request-Id (header) | The id this request is recorded under. Present on media endpoints and on every error; quote it in support requests. |
On a stream, set stream_options.include_usage to receive the same object in the final chunk. Token counts are reported in both the chat vocabulary (prompt_tokens / completion_tokens) and the newer one (input_tokens / output_tokens), so one client library reading either shape sees the same numbers.
Which provider served you is not disclosed. Oxyy routes across multiple upstreams for availability and price, and does not return the provider that served a given request. The price you are charged is the price you were quoted for the model, whichever upstream answered.