Tito Rate Limits
Tito does not publish fixed numeric rate limits for the Admin API in its public documentation. The documentation does define pagination behavior for collection endpoints: results are returned in pages via the page[number] and page[size] query parameters, with a default page size of 100 and a maximum page size of 1000, and pagination metadata (current_page, next_page, total_pages, total_count, per_page, overall_total) returned in a meta object. Clients should paginate large result sets rather than attempting to pull all records in a single request, and should handle throttling defensively.
Tito Rate Limits is the machine-readable rate-limit profile for Tito on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and records.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Event Ticketing, Ticketing, Rate Limiting, and Quotas.
Limits
Policies
Sources
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/tito-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.