Transitapp Rate Limits
Transit publishes explicit rate limits for its free API tier: up to 5 requests per minute and 1,500 requests per month per access key. These are hard caps on the free tier; exceeding them requires arranging higher limits with Transit's partnerships team, whose ceilings are negotiated rather than published. Because real-time transit data changes frequently, Transit recommends pacing polling (for example, refreshing a departure board every 10-30 minutes) to stay within the free monthly budget.
Transitapp Rate Limits is the machine-readable rate-limit profile for Transit on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Transit, Public Transportation, Real-Time, 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/transitapp-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.