---
title: "This key's plan and month-to-date usage"
method: GET
path: "/usage"
tags: ["utilities"]
---

# This key's plan and month-to-date usage

`GET /usage`

## Request

- Base URL: `https://api.cars-data.com/v1`
- URL: `https://api.cars-data.com/v1/usage`
- Auth: one of:
  - API key in header `X-Api-Key`
  - HTTP bearer

## Response `200`

OK

- UsageEnvelope
  - `data` Usage
    - `plan` 'demo' | 'apify' | 'free': `demo` — the self-serve tier, 40 cars. `apify` — the paid channel, metered and billed by Apify. `free` — **legacy and deprecated.** Nothing has issued one since 2026-10-06 and the plan is being removed; it can still appear on a key granted by hand before that date.
    - `quota` integer
    - `resets_at` string, date-time
    - `used` integer: Calls counted this month. Counting is best-effort and is known to under-count; it is not a billing record.
  - `meta` Meta
    - `last_synced_at` string, date-time, required
    - `locale` string
    - `units` 'metric' | 'imperial'

## Other responses

- `401`: No key, or a key we do not know. `WWW-Authenticate: Bearer` on the MCP surface. The MCP server needs no key at all; a REST demo key is one click away. On the two x402 routes a request with no key gets `402` instead, with the price.
- `403`: RFC 9457 problem document.

---

[API](https://skmtc.dev/cars-data/apis/cars-data-com-api.md) · [All operations](https://skmtc.dev/cars-data/apis/cars-data-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cars-data/apis/cars-data-com-api/revisions/4aeb6b2b5c5f?raw)