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.

5 Limits Throttle: 429 Quota: 429
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