# GET /api/mcp/data/me/usage

> How much of my monthly API allowance is left, and which endpoints have I been calling?

Returns the calling account's usage for the current month in the same unit the allowance is enforced in: data requests used, the plan's allowance, what remains and when the counter resets. It adds the live rate-limit position for this token, the number of calls per endpoint this month with each endpoint's docs page, the count of active tokens on the account, and the unknown paths this token has hit in the last seven days, which is the quickest way to spot a client built against a path that does not exist. The same numbers appear on the account page. The call costs nothing against the allowance.

- **Family:** Account and index (https://apexvol.com/developers/account-api)
- **Plan:** Basic and above. Every call needs `Authorization: Bearer avmcp_<token>`; tokens are issued to paid and trial accounts under Account, then API Access.
- **Units:** used, limit and remaining count upstream data requests, not API calls; one call can spend more than one and a cached call spends none. Times are ISO 8601 in UTC.
- **Basis:** The account's counter is the one the 429 budget gate reads; per-endpoint counts come from the per-month usage hash the account page also shows. Integration tokens issued by an admin have no allowance and report limit null.
- **Background:** https://apexvol.com/learn/options-data-api

## Parameters

No parameters.

## Request

```bash
curl -H "Authorization: Bearer avmcp_YOUR_TOKEN" \
     "https://apexvol.com/api/mcp/data/me/usage"
```

## Response (captured 2026-09-08)

Real response, lists cut to the rows nearest the money. The envelope is `{"success": true, "data": ...}`.

```json
{
  "success": true,
  "data": {
    "calls_this_month": 0,
    "docs": "https://apexvol.com/docs/api/guides/rate-limits",
    "endpoints": [],
    "limit": 10000,
    "month": "2026-09",
    "percent_used": 0.2,
    "plan": "pro",
    "rate_limits": {
      "per_hour": 1000,
      "per_minute": 60,
      "remaining_hour": 1000,
      "remaining_minute": 60
    },
    "remaining": 9981,
    "resets_at": "2026-10-01T00:00:00+00:00",
    "this_token": {
      "label": "local capture 2026-09-08",
      "token_id": "CAP4F1221",
      "unknown_paths_7d": {}
    },
    "tokens_active": 1,
    "unit": "data_requests",
    "used": 19
  }
}
```

## Fields

- `used, limit, remaining, percent_used`: The month's meter. limit is null for an admin-issued integration token.
- `resets_at`: When the counter returns to zero: the first of next month, UTC.
- `rate_limits`: per_minute, per_hour and what remains of each for this token right now.
- `calls_this_month, endpoints[]`: Calls per endpoint rule, most-called first, each with its docs page.
- `tokens_active`: Active tokens on the account, this one included.
- `this_token.unknown_paths_7d`: Paths under /api/mcp/data that 404d for this token in the last seven days, with counts.

## Errors

- `401`: no or revoked token
- `429`: Retry-After seconds
- `403`: no active paid plan on the account
- Full list: https://apexvol.com/developers/errors

## Ask it in an MCP client

- How much of my ApexVol API allowance is left this month?
- Which endpoints have I called most this month?
- When does my API usage counter reset?

Conventions for units, bases and timestamps: https://apexvol.com/developers/conventions