Mobula Rate Limits
Mobula governs API usage primarily through a monthly credit (compute-unit) allowance rather than fixed requests-per-second throttling. Each plan (Free, Start-up, Growth, Enterprise) carries a monthly credit budget; most REST calls cost 1 credit and heavier endpoints cost more. When the monthly credit allowance is exhausted, further requests are rejected until the budget resets or the plan is upgraded. WebSocket streams also draw down credits (1 credit per minute open plus underlying endpoint cost). Specific per-second request ceilings are not published and are not reconciled here.
Mobula Rate Limits is the machine-readable rate-limit profile for Mobula on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, measuring credits, assets, and requests.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Crypto, Web3, Market Data, Blockchain, and Wallet.
generated, dated 2026-07-01.
Limits
Policies
Sources
- https://mobula.io/pricing
- https://docs.mobula.io/pricing
- https://docs.mobula.io/rest-api-reference/introduction
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.