Messente Rate Limits
Messente applies fair-use throttling to its REST API to protect delivery quality and downstream carriers. Sustained request throughput and messaging send rate (messages per second) are governed per account and can be raised for high-volume senders on request. Bulk sending is designed to be submitted via the bulk Omnimessage endpoint rather than many concurrent single-message calls. Specific numeric limits are not published as fixed public values and are set per account.
Messente Rate Limits is the machine-readable rate-limit profile for Messente on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, messages_per_second, and recipients.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include CPaaS, Messaging, SMS, Rate Limiting, and Quotas.
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/messente-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.