Respond Rate Limits
The respond.io Developer API limits each API call method to 5 requests per second. When the limit is exceeded the API returns HTTP 429 (Too Many Requests) with a Retry-After header indicating how long to wait. Enterprise agreements can negotiate higher API limits. Per-channel messaging is additionally subject to the upstream channel provider's limits (for example WhatsApp Business Platform messaging tiers), which are not reconciled here.
Respond Rate Limits is the machine-readable rate-limit profile for Respond.io on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and messages.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Messaging, Omnichannel, Customer Conversations, WhatsApp, and AI.
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/respond-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.