Cubic Rate Limits
Cubic publishes real, numeric limits for the Umo IQ Public Feed in its feed documentation (Public XML Feed revision 1.24, section "Limits on Amount of Data"). They are volume and cardinality caps rather than request-per-second quotas, and the API returns NO rate-limit response headers — no X-RateLimit-*, no RateLimit-*, no Retry-After were present on any of the nine commands probed on 2026-09-19, so a client cannot observe its remaining budget at runtime and must self-police against the documented numbers.
Cubic Rate Limits is the machine-readable rate-limit profile for Cubic on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring characters, routes, stops, predictions, and minutes.
Limit state is signalled in the published, observed, and note response headers.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, serviceUnavailable, and note.
Tagged areas include Transportation, Public Transit, and Rate Limiting.
publishedobservednote
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.