Rudderstack Rate Limits
RudderStack publishes very little runtime rate-limit information. The HTTP tracking API documents a 429 "Too many requests" status but NO request-per-second cap, and the only numeric per-API rate limit anywhere in the documentation is on the User Suppression API, expressed as hourly token budgets. The real commercial constraint is the monthly event quota attached to the plan tier. Payload limits (32 KB per call, 4 MB per batch, 200-level JSON nesting) are documented and hard.
Rudderstack Rate Limits is the machine-readable rate-limit profile for RudderStack on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring tokens, requests, and events.
The profile also includes response codes documented for throttled, payloadTooLarge, and badRequestOnOversize.
Tagged areas include Customer Data Platform, CDP, Event Streaming, Rate Limiting, and Quotas.
Limits
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/rudderstack-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.