Rate limits
Each developer key has its own rate limit, measured in requests per minute. New keys are created with a limit of 60 requests per minute. Your plan also caps the rate of each key, and the lower of the two applies:
MCP OAuth connections, which do not use a key, are limited to 60 requests per minute. Exceeding a rate limit returns
429 Too Many Requests. Rate-limited requests are not charged.
Handling 429
Check the response body to identify the cause:detail: "Rate limit exceeded"means the key exceeded its request rate. Retry with exponential backoff and spread out bursts of calls. This response does not includeRetry-After.detail.error_code: "PLAN_LIMIT_REACHED"means the account does not have enough credits for the call.detail.balanceis what is left anddetail.requiredis the call’s price. Wait fordetail.resets_ator upgrade the plan.Retry-Aftergives the seconds until credits refresh when that time is known; immediate retries fail the same way.
Metering
Every tool call is recorded per key. For each key, Nikiwa tracks:- Current-period units, the usage in the current calendar month (
YYYYMM, UTC). - Total calls and total units, durable lifetime counters.
- Per-tool breakdown, calls and units grouped by tool name.
The Tools API and the MCP server are metered and rate-limited independently, each on its own per-key window. Both draw on the same credit balance.