Uniblock · Rate Limits

Uniblock Rate Limits

Uniblock enforces rate limits at the plan level using compute units per second (CU/s) along with a monthly CU envelope. Limits are bound to the project's API key. Exceeding the rate returns HTTP 429; clients should back off, batch, cache, or upgrade to a higher plan. Specific retry headers are not documented publicly.

Uniblock Rate Limits is the machine-readable rate-limit profile for Uniblock on the APIs.io network, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, measuring compute_units_per_second.

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 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Blockchain, Web3, and Rate Limiting.

5 Limits Exhausted: HTTP 429 Quota: 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
BlockchainWeb3Rate Limiting

Limits

Startup plan rate project
compute_units_per_second · second
1000
Free Startup plan; 40M CUs per month.
Growth plan rate project
compute_units_per_second · second
2000
Growth plan; 500M CUs per month.
Pro plan rate project
compute_units_per_second · second
8000
Pro plan; 2B CUs per month.
Business plan rate project
compute_units_per_second · second
20000
Business plan; 5.5B CUs per month.
Enterprise plan rate contract
compute_units_per_second
custom
Negotiated CU/s and dedicated nodes per contract.

Policies

Backoff Strategy
On HTTP 429, implement retry with exponential backoff or brief delay before re-submission.
Caching and Batching
Reduce CU consumption by lowering polling frequency, batching requests, and caching responses where possible.
Plan Upgrade
Sustained throughput needs above plan limits should be addressed by upgrading plan tier rather than retrying past the limit.
Plan-Scoped Enforcement
Rate limits are enforced at the Uniblock plan level per project, not globally per account.

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/uniblock-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.