Plan limits
These are the current self-serve allowances. Legacy and custom plans can differ; the dashboard shows your organization’s entitlement. Enterprise subscriptions are managed by the Context team. For Enterprise subscriptions, plan changes, pauses, cancellation, Auto-Topup, spend alerts, and payment-method updates aren’t available in the dashboard; contact us to change them. Invoices stay visible in Billing.
New Free organizations also have a limit of 10 requests per minute across the organization. Developer subscriptions started before November 7, 2026 keep 10,000 credits per month.
Organizations created before concurrency limits keep per-minute limits per API key on every plan: 30 on Free with a work email, 10 on Free with a personal email, 60 on Developer, 200 on Pro, 600 on Growth, and 700 on Scale.
Paused monitors count toward the limit. Batches in
queued, running, or cancelling count as active. Rate limits explains both limit types and the separate management buckets.
Refills
Paid plans refill monthly, including annual subscriptions, on the billing-anchor day at 00:01 Pacific. A refill resets the balance to the plan allowance; it waits for the renewal invoice to be paid. Resolve payment failures in Billing to release held refills and top-ups.Insufficient credits
The API returns HTTP 402 witherror_code: "USAGE_EXCEEDED" when authenticated requests cannot pass the credit check or reserve a batch’s quoted credits. The rejected operation is not executed or charged. Authentication remains valid; reconnecting or retrying the same request immediately does not restore credits.
Inspect your balance with GET /org/usage, or the MCP get-usage tool. Both cost no credits and remain available at zero balance, subject to normal authentication, permissions, and request limits. Retry when the balance covers the operation. An available refill may suffice; a subscription purchase is not the only possible recovery. A failed payment or billing pause can delay available credits.
The error envelope contains message, error_code, key_metadata, and request_id. request_id also appears in the X-Request-Id header. Its error_data contains:
For example, an admission check needing 10 credits with 3 remaining returns:
403 PAID_PLAN_REQUIRED (a feature entitlement), 403 INSUFFICIENT_PERMISSIONS (key access), and 429 RATE_LIMITED (temporary throttling). Adding credits does not grant a missing feature entitlement. For temporary throttling, follow Retry-After; for genuine credential failures, repair authentication.
Concurrency limits
Organization concurrency exhaustion returns 429 RATE_LIMITED. Itserror_data reports is_authenticated, limit_type: "concurrency", the effective limit, available slots in remaining, retry_after_seconds, known credits_remaining, and credits_charged: 0.
should_retry: false means do not immediately repeat the unchanged request. Follow Retry-After and retry when retry_condition: "available_concurrency" is met. recovery_options lists "wait_for_in_flight_requests" and "increase_concurrency_limit"; info_url opens subscription settings. A subscription change may provide a higher limit, depending on the account’s plan and custom allowances. Waiting for an in-flight request to finish also restores capacity without changing the subscription.
Rate-limit headers specify when to retry. Concurrency responses set X-RateLimit-Mode: concurrency and omit X-RateLimit-Reset. Per-minute limits include a reset timestamp.
Change a plan
An upgrade to more monthly credits takes effect after payment succeeds. The billing term restarts without proration, and the new allowance is added to the remaining balance until the next refill. Outstanding Auto-Topup usage settles at the previous plan’s rate. Annual upgrades refund unused prepaid months. Downgrades and annual-to-monthly changes take effect at period end. Current limits and monthly refills continue until then. Undo a scheduled change in Billing before pausing, cancelling, or choosing another change.Auto-Topup and spend alerts
Auto-Topup is enabled by default at checkout. When the balance falls below 1,000 credits, it adds a 1,000-credit block at the plan’s rate. Accrued usage is invoiced each time it reaches $10 on Developer or $100 on other plans, and at renewal. With Auto-Topup off or unavailable, insufficient balance returns402 USAGE_EXCEEDED.
Spend alerts notify Owners and Admins at selected budget thresholds. They are notifications, not a hard spending cap: requests, monitors, and Auto-Topup keep running. Turning Auto-Topup off clears its alert budget. Payment failure can put both refills and top-ups on hold.