Tabby Rate Limits
Tabby publishes exact rate limits with numbers, split by key environment and by operation class. Limits are enforced per API key and measured per operation, with Create Session treated as its own class. Exhaustion returns HTTP 429. The API returns no rate-limit response headers of any kind, so the published numbers are the only budget signal an integrator has — there is nothing to read at runtime.
Tabby Rate Limits is the machine-readable rate-limit profile for Tabby on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the rateLimitLimit, rateLimitRemaining, rateLimitReset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, authFailure, and forbidden.
Tagged areas include BNPL, Payments, and Rate Limiting.
rateLimitLimitrateLimitRemainingrateLimitResetretryAfter
Limits
Sources
- https://docs.tabby.ai/introduction/technical-requirements#rate-limit
- https://docs.tabby.ai/pay-in-4-custom-integration/webhooks
- https://docs.tabby.ai/api-reference/disputes
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.