---
title: "Return usage and current rate-limit state for the calling key."
method: GET
path: "/usage"
---

# Return usage and current rate-limit state for the calling key.

`GET /usage`

## Headers

- `Oximy-Version` '2026-06-29'

## Response `200`

Calling key usage.

- UsageResponse
  - `object` 'usage', required
  - `request_id` string, required
  - `as_of` string, date-time, required
  - `data` object, required
    - `key_id` string, required
    - `key_prefix` string, required
    - `mode` 'live', required
    - `scopes` string[], required
    - `api_version` string, required
    - `requested_version` string, nullable
    - `effective_version` string, required
    - `supported_versions` string[], required
    - `last_used_at` string, date-time, nullable
    - `usage_count` number, required
    - `rate_limit` RateLimitState, required
      - `limit` number, required
      - `remaining` number, required
      - `reset_at` string, date-time, required

## Other responses

- `304` — Not modified. Conditional GET responses do not consume rate-limit quota.
- `400` — Invalid parameters.
- `401` — Missing or invalid API key.
- `403` — The API key does not have the required scope.
- `404` — The requested resource was not found in the calling key's workspace scope.
- `409` — Conflict or idempotency replay conflict.
- `429` — Rate limit exceeded.
- `500` — Unexpected server error.

---

[API](https://skmtc.net/oximy/apis/oximy-public-api.md) · [All operations](https://skmtc.net/oximy/apis/oximy-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/oximy/oximy-public-api/revisions/36cc62fb2aaf/schema)