Limits and usage
Limits apply across the account and its keys. Creating another key does not increase capacity or reset usage.
Current limits
Section titled “Current limits”| Resource | Limit | Scope |
|---|---|---|
| Active API keys | 5 | Account |
| New keys | 5 per hour | Account, rolling hour |
| Key lifetime | 30, 90, or 365 days; 90 default | Key |
| Pro code searches | 1,000 per day | Account, UI and all keys together |
| API search starts | 10 per minute | Account, fixed minute windows |
| Active API searches | 1 | Account |
| Workspace-list requests | 60 per minute | Account, fixed minute windows |
| API ingress requests | 120 per minute | Client IP, fixed minute windows |
| Query length | 1–2,048 trimmed characters | Search |
| JSON body | 4,096 bytes, known length | Request |
| Search hits | 100 maximum | Stream |
| Search runtime | 45 seconds maximum | Stream |
| Event frame | 65,536 bytes maximum | Stream |
| Event output | 1,048,576 bytes maximum | Stream |
Search allowance resets at 00:00 UTC. API execution requires current eligible Pro access even though a Free account can create and manage keys. Consult your account’s usage display for its current entitlement and consumption.
Fixed minute windows mean requests either side of a minute boundary can occur close together. Do not rely on that behavior to sustain a burst. Shared service capacity is separate from these account limits and may be exhausted even when your account has remaining allowance.
Responding to 429
Section titled “Responding to 429”Read the JSON error code and Retry-After response header. Wait at least the indicated number of seconds, then use a bounded retry policy. For search_quota_exceeded, the daily reset or a change to account allowance is required; repeatedly retrying after a short delay will not restore the budget.
Prefer a queue with one active search per account. Share that queue across application processes rather than creating independent high-concurrency clients for each API key.
What consumes a search
Section titled “What consumes a search”The UI and API share the daily search ledger. A request is reserved before execution. Failed requests before stream headers are handled with a refund; after streaming begins, partial results and client cancellation still count. A retry is a separate search. Listing workspaces does not consume this search allowance, but does consume metadata and ingress request budgets.
Limits are operational bounds, not a latency or corpus-coverage guarantee. Read the start event’s advertised limits and retain terminal completeness metadata.