Rate limits & errors

REST and MCP share a single daily request limit per account. Every response carries headers so you can track usage, and errors follow a consistent JSON shape.

Daily limits

One counter covers both the REST API and MCP tool calls. It resets at 00:00 UTC.

Need more? Compare plans.

Rate-limit headers

Every counted response includes these headers:

When you hit the limit

Over the limit, the REST API returns 429 Too Many Requests with the error envelope below. The MCP server instead returns a normal tool result whose text explains the limit and links to upgrade — so your agent can relay it in the conversation rather than surfacing an opaque transport error.

{ "error": { "code": "rate_limited", "message": "Daily call limit exceeded.", "status": 429 } }

Error format

Every non-2xx REST response uses the same envelope:

{
  "error": {
    "code": "not_found",
    "message": "Stock not found.",
    "status": 404
  }
}