Mailpace Rate Limits
MailPace applies sending rate limits to protect deliverability when large volumes of email are sent over short periods. The send endpoint returns HTTP 429 Too Many Requests when limits are exceeded. Per-request structural limits also apply - a maximum of 50 recipients in the To field and a total message size of 50 MB. Specific numeric per-second/per-minute send rates are not published and are not reconciled in this artifact.
Mailpace Rate Limits is the machine-readable rate-limit profile for MailPace on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring emails, recipients, and bytes.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Email, Transactional Email, Messaging, SMTP, and Privacy.
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/mailpace-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.