Request counts, token breakdowns, and latency for every inference request in a project.
arkor.ai/<org>/<project>/usage aggregates chat completions made through the project: endpoint traffic, playground messages, and CLI calls alike. One request equals one row, recorded when the request finishes. Only requests that pass ingress validation, authentication, and quota checks are counted — attempts rejected before dispatch (bad API key, malformed body, an Arkor 429 quota rejection) produce no row, so usage is not a record of every call your endpoint received. Requests that fail after dispatch do count: a request an external provider rejected with its own 429/529 backpressure, or one that failed mid-generation, appears as a failed row.
A per-day bar chart over the range, toggleable between request counts and stacked token breakdowns. Days are UTC buckets of request arrival time.
Group requests by:
| Dimension | Meaning |
|---|---|
model | Base model served |
deployment | Which endpoint received the traffic |
user | Cloud / CLI account that made the request |
endUser | Your X-Arkor-End-User-Id header values |
session | Your X-Arkor-Session-Id header values |
The endUser and session dimensions are high-cardinality and limited to 31-day windows; on the 90-day preset the dashboard falls back to the model breakdown and says so.
To make the endUser and session dimensions useful, send the attribution headers with your API calls. They are free-form labels, capped at 256 characters, and never affect authorization. See Attribution headers.
