Mobula · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring credits, assets, and requests.

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.

6 Limits Throttle: 429
CryptoWeb3Market DataBlockchainWalletReal TimeRate LimitingQuotasThrottling

Limits

Monthly Credits (Free) account
credits
10000
Free tier monthly credit allowance; most REST calls cost 1 credit.
Monthly Credits (Start-up) account
credits
125000
Start-up tier monthly credit allowance.
Monthly Credits (Growth) account
credits
1250000
Growth tier monthly credit allowance; unlocks WebSocket feeds.
Monthly Credits (Enterprise) account
credits
unlimited
Enterprise tier; unlimited credits under contract.
WebSocket Assets Per Subscription connection
assets
100
A single market WebSocket subscription can track up to 100 assets.
Per-Second Request Ceiling account
requests
see provider documentation
No fixed per-second ceiling is published; governance is via monthly credits.

Policies

Credit-Based Governance
Usage is metered by monthly credits; heavier endpoints consume more credits per call.
Tiered Allowances
Credit budgets rise across Free, Start-up, Growth, and Enterprise plans.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources