# Usage Tracking

Source: https://aiand-docs-staging.pages.dev/billing/usage/

Usage data is available in two places: the **console dashboards** (human-friendly) and the **Analytics API** (programmatic).

## Console dashboards

At [console.aiand.com](https://console.aiand.com), the dashboard shows:

- Current credit balance.
- Spend over the last 24 hours, 7 days, and 30 days.
- Top models by request count and by cost.
- Recent requests with status, latency, and cost.

## Analytics API

For automated reporting, query the [Analytics](/analytics/metrics/) endpoints:

- `GET /analytics/metrics` — time-series of requests and tokens.
- `GET /analytics/summary` — aggregated totals over a range.
- `GET /logs` — individual request rows with cursor pagination.

Each endpoint's page lists the `range` values it accepts.

From a terminal, `aiand usage --range 30days` from the [ai& CLI](/cli/) shows requests and tokens for the range, compared with the previous one.

`GET /analytics/metrics` and `GET /analytics/summary` return requests and tokens for the range. `GET /analytics/metrics` also returns tokens per second, latency, and time to first token. `GET /logs` rows include each request's cost and currency. For the remaining balance, use the [Balance API](/billing/balance/).

## Per-request cost

Send `X-Aiand-Metrics: true` with a request to receive `X-Cost` and `X-Cost-Currency` headers carrying the exact cost of that request in your billing currency. Streaming responses emit the same values in the final trailer event. See [Response Headers](/reference/response-headers/) and [Streaming Events](/reference/streaming-events/).

<Aside type="note">
  The analytics API is rate-limited and cached for 120 seconds — fine for dashboards, not suitable for sub-second polling.
</Aside>