Tabby Rate Limits
Tabby does not publish formal per-merchant request-rate or throughput numbers in its public documentation. Practical limits documented below are derived from the OpenAPI surface and behavioural notes in the merchant docs. Webhook delivery has explicit retry semantics (1m timeout, 4 retries with 1-4 minute exponential backoff).
Tabby Rate Limits is the machine-readable rate-limit profile for Tabby on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions.
The profile also includes response codes documented for throttled, quotaExceeded, authFailure, and forbidden.
Tagged areas include BNPL, Payments, and Rate Limiting.
Limits
Sources
- https://docs.tabby.ai/api-reference/overview
- https://docs.tabby.ai/api-reference/disputes
- https://docs.tabby.ai/pay-in-4-custom-integration/webhooks
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/tabby-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.