Hosted beta
API limits
Plan around workspace allowances, request sizes, and the shared capacity of the hosted beta.
These are current beta limits, not reserved throughput. API keys and console tests share workspace limits.
| Limit | Current value |
|---|---|
| Workspace free allowance | Up to 100 completed Decisions per UTC day; console tests share it; returned failure Decisions count |
| Shared production evaluation capacity | 40 free and 40 paid evaluation attempts per UTC day across all workspaces, no borrowing between pools |
| Shared throughput | One evaluation at a time, at most 30 attempts/minute across the deployment |
| Workspace requests | 60 authenticated requests/minute, including policy reads and replays |
| Workspace evaluations | Up to 4 running operations and 60 evaluation attempts/minute |
| Policy validation | 1,000 validations per workspace per UTC day; saves and evaluations also validate |
| Policy | 64 KiB UTF-8 source; at most 25 rules |
| Input | JSON object; at most 16 KiB after JSON serialization |
| Entire JSON request | At most 493,568 bytes; individual policy/input limits still apply |
| Managed policies | 50 per workspace, including archived policies |
| Service accounts / keys | 10 active service accounts; 2 active credentials per account |
Daily limits reset at 00:00 UTC. The workspace allowance is not a reservation of the smaller shared free pool: requests can receive 429 before reaching 100. Failed upstream attempts can consume shared capacity even when the customer is not charged. Additional authentication limits apply to networks and credential verification. Bought credit carries forward, but buying credit does not increase daily capacity or concurrency. Use Retry-After instead of assuming that a retry will be admitted.