Whippy Rate Limits
The Whippy Public API enforces per-organization request rate limits and bounded page sizes on list endpoints (limit default 50, max 500), with per-request maximums on bulk operations such as adding contacts to a sequence (1-4000 contacts per call). Specific requests-per-minute / requests-per-second ceilings are governed per account and tier and are not reconciled in this artifact; messaging throughput is additionally bounded by each plan's monthly credit allocation and carrier throughput.
Whippy Rate Limits is the machine-readable rate-limit profile for Whippy on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring results, contacts, requests, and messages.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Communication, Messaging, SMS, Email, and Campaigns.
Limits
Policies
Sources
- https://docs.whippy.ai/docs/getting-started
- https://docs.whippy.ai/changelog/changes-to-max-limits
- https://www.whippy.ai/pricing
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/whippy-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.