Usage & analytics
Docs · Billing & usage

Usage & analytics

Request logs and usage per workspace, and organization-wide analytics by workspace and by member.

Two places show where requests and money went. Usage is per workspace and is open to everyone with access. Analytics is organization-wide and is for admins.

Usage#

Open Usage in the sidebar to see what the current workspace has used. Switch workspace from the workspace switcher, or choose all workspaces to see them together.

What it shows#

  • Range: the last 24 hours, 7 days, or 30 days.
  • Summary cards: requests, input tokens, output tokens, and spend for the range and filters.
  • Activity: one row per request with time, model, API key, tokens, cost, latency, and status. Expand a row to see its request ID and the breakdown of the cost.

Filter#

Filter by model, API key, and endpoint. Each field picks values to include. You can share a filtered view: the filters are in the page URL, and links from the API keys page open Usage already filtered to that key.

Find one request#

Every response has an X-Request-Id header, and you can set your own. Expand a row in Activity to see its request ID and match it against yours. See Reasoning & tracing.

How long logs are kept#

Request logs are kept for a limited time (45 days by default). Older requests no longer appear. Times are shown in your browser's time zone.

Analytics#

Open Analytics in the sidebar of an organization. It is visible to admins only, and organizations only: a personal space has just one person, so there is nothing to break down.

Analytics always shows the current month so far, in UTC, and has three parts whose totals agree:

PartWhat it shows
SummaryTotal spend, requests, tokens, and the number of API keys that currently work.
By workspaceSpend, requests, and tokens for each workspace.
By memberSpend, requests, and tokens for each member. Spend is attributed to the owner of the key that made the request, not to whoever created the key.

Things to know:

  • Only billed requests are counted. A failed request that was not charged does not appear.
  • Workspaces and members with no spend are still listed, so you can see who is idle. A deleted workspace or a removed member appears only if it has spend in the period, marked as such, because that money was spent.
  • Each list is ordered by spend, highest first.
  • The active keys number is a count as of now, not for the period, and it excludes disabled and expired keys.

Usage and budgets#

Usage tells you what happened. Budgets let you act on it: a table there shows spend against each limit.