Usage and limits

Account allowance

Open Usage to see your allowance, completed requests, requests in progress, and reset time. A configured daily allowance resets at 00:00 UTC.

Every key on your account shares this allowance. REST data requests, dashboard data requests, and MCP data tool calls each reserve one unit before running. Concurrent requests count against the same allowance.

What counts

• Successful data requests consume one unit.
• Failed data queries release their reservation.
• Sign-in, key management, checking usage, and MCP connection handshakes do not consume data allowance.

Handle request limits

When your allowance is exhausted, REST returns 429. Honor Retry-After rather than immediately repeating the request. The reset header is a Unix timestamp in seconds.

HTTP/1.1 429 Too Many RequestsX-RateLimit-Remaining: 0X-RateLimit-Reset: <UTC reset timestamp>Retry-After: <seconds until reset>{"error":{"type":"rate_limited","status":429,"message":"allowance_exhausted"}}

Burst protection can also return 429 before a daily allowance is exhausted. Use bounded exponential backoff and respect the server’s retry time.