Rate limits

• When the active top-up balance is $100 or more, the effective limits move down one row in this table automatically.
• The limits object also reports global_tokens_per_day and per_user_tokens_per_day, a 10-million-token daily guardrail by default. Both fields are informational; no Developer API surface enforces a daily token limit.
• Per-user overrides are available for production integrations. Contact StefanBrain if you need more throughput.

• The API wallet limits wallet-billed spend. A request returns 429 api_wallet_exhausted when the balance minus active holds is below one hold, so the wallet can refuse new work before $0. See Pricing.
• A per-key budget returns 429 api_key_budget_exhausted when exhausted.
• For standard member accounts, the plan’s monthly usage pool controls MCP usage and returns 429 monthly_usage_limit_reached when exhausted. Contracted partner accounts can have account-specific billing terms.

​

Rate-limit response

{
  "error": {
    "message": "Daily request limit reached (25000/25000 requests today on the Elite plan). Resets at 2026-08-28T00:00:00.000Z. Job status/result polling never counts against rate limits.",
    "type": "rate_limit_error",
    "code": "request_per_day"
  },
  "limits": {
    "per_minute": 120,
    "per_user_per_minute": 240,
    "per_day": 25000,
    "global_tokens_per_day": null,
    "per_user_tokens_per_day": 10000000
  },
  "observed": {
    "minute_count": 3,
    "user_minute_count": 3,
    "day_count": 25001
  },
  "plan": "elite",
  "reset_at": "2026-08-28T00:00:00.000Z",
  "state": {
    "current": "normal",
    "expires_at": null
  }
}