Orb Billing Rate Limits
Orb does not publish a hard, numeric rate limit for production API usage or a maximum request payload size; the docs instead ask customers to notify Orb before changing request volume or payload size by an order of magnitude from initial setup. The event ingestion path (POST /ingest) is the primary high-throughput surface and supports batched events per request. Test-mode event ingestion is constrained (documented around 2,000 events/minute and ~10 requests/second). When limits are exceeded the API returns HTTP 429 Too Many Requests, and Orb recommends retrying with exponential backoff. Specific production per-endpoint values are not reconciled in this artifact.
Orb Billing Rate Limits is the machine-readable rate-limit profile for Orb on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, events, and bytes.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Billing, Usage-Based Billing, Metering, Subscriptions, and Rate Limiting.
Limits
Policies
Sources
- https://docs.withorb.com/api-reference/rate-limits
- https://docs.withorb.com/events-and-metrics/event-ingestion
- https://docs.withorb.com/api-reference
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.