Skip to main content
GET
Count the calling credential's own requests over the last 7 days, by route and status (not by MCP tool)
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

Counts your credential’s own requests over the last 7 days, by UTC day, route and status class, so a client can see its request mix and error rate without keeping its own log.

Authorization

GET /api/v2/me/usage requires no permission. Any Platform API credential can call it. It counts only the requests filed under the calling credential; every credential of one External Application (its access tokens and its companion key) shares the app’s requests. A request that sends any query parameter or a body is refused with 400 and code bad_request. One call can read up to 20,000 records, so this endpoint spends from the expensive rate-limit class, not from read.

Response

routeKey is the method and declared route template, never the raw path. Look up a single request with GET /api/v2/requests/{requestId}.

Example

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Response

The calling credential's request counts

data
object
required
meta
object
required