Usage - Exo

What this family does

GET /v1/usage returns metered units bucketed over a time window and grouped by subject, key or capability, so a developer reselling Exo to their own users can attribute cost per end user. Buckets are aligned to startTime, and only non-empty buckets come back. A range with no usage is an empty list with a 200.

Routes

Method	Path	Scope	What it does
`GET`	`/v1/usage`	`usage:read`	Bucketed usage metering

The shape of a call

Read metered usage.

curl "https://api.get-exo.com/v1/usage?startTime=2026-07-01T00:00:00Z&endTime=2026-08-01T00:00:00Z&groupBy=subject" \
  -H "X-Exo-API-Key: $EXO_KEY"

import httpx

response = httpx.get(
    "https://api.get-exo.com/v1/usage",
    headers={"X-Exo-API-Key": EXO_KEY},
    params={
        "startTime": "2026-07-01T00:00:00Z",
        "endTime": "2026-08-01T00:00:00Z",
        "groupBy": "subject",
    },
)

const params = new URLSearchParams({
  startTime: "2026-07-01T00:00:00Z",
  endTime: "2026-08-01T00:00:00Z",
  groupBy: "subject",
});
const response = await fetch(`https://api.get-exo.com/v1/usage?${params}`, {
  headers: { "X-Exo-API-Key": process.env.EXO_KEY! },
});

The response:

{
  "buckets": [
    {
      "startTime": "2026-07-01T00:00:00Z",
      "endTime": "2026-07-02T00:00:00Z",
      "groups": [
        { "subject": "customer_6412", "capability": null, "units": { "readUnits": 412, "embedTokens": 1840 } }
      ]
    }
  ]
}

Traps

This is an organization-wide view. It aggregates every subject, so it requires usage:read. An admin key also qualifies. A plain read key is refused. Grouping by subject uses your own subject keys. Usage recorded for the key owner is grouped separately from usage recorded for a provisioned subject.

API reference

Base URL, authentication, and the conventions every route shares.

Errors

The problem envelope and the full code catalogue.

Wipe the sandbox partition

Bucketed usage metering

⌘I

​What this family does

​Routes

​The shape of a call

​Traps

​Related