---
title: "Get usage metrics for current user"
method: GET
path: "/billing/usage"
tags: ["Billing"]
---

# Get usage metrics for current user

`GET /billing/usage`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/billing/usage`
- Auth: HTTP bearer

## Query parameters

- `days` integer

## Response `200`

Usage data

- UsageMetrics
  - `daily` object[]
    - `date` string, date
    - `check_count` integer
    - `tokens_in` integer
    - `tokens_out` integer
  - `daily_unavailable` boolean: True when the daily usage rollup could not be read. Distinguishes a failed lookup from a genuinely empty history, both of which return an empty `daily` array.
  - `summary` object
    - `checks_used` integer
    - `checks_included` integer
    - `overage` integer
    - `estimated_overage_cost` number
    - `period_start` string, date-time
    - `period_end` string, date-time

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)