Aptos · Rate Limits

Aptos Rate Limits

Aptos Labs provides limited anonymous access to the Fullnode REST, Indexer GraphQL, and Transaction Stream APIs on a per-IP basis without an API key. Authenticated access via a Geomi API key grants significantly higher limits, metered in compute units (CU). A deprecated per-5-minute CU system limit has been replaced with granular HTTP-level request limits that vary by subscription status (no payment method vs. payment method attached). Throttled requests receive HTTP 429 responses.

Aptos Rate Limits is the machine-readable rate-limit profile for Aptos on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests_per_period and compute_units_per_month.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Blockchain, Web3, Move, Layer 1, and Rate Limiting.

5 Limits Throttle: 429
BlockchainWeb3MoveLayer 1Rate Limiting

Limits

Anonymous per-IP access ip_address
requests_per_period
-1
Aptos Labs provides limited free access without an API key, throttled per source IP. Exact per-minute or per-second caps are not published; meaningfully lower than authenticated access.
Geomi free tier (no payment method) — compute units api_key
compute_units_per_month
-1
Organizations without a payment method receive $10/month in free CU credits. Service pauses when the monthly credit is exhausted. Exact CU-per-request values vary by endpoint type.
Geomi paid tier (payment method attached) — compute units api_key
compute_units_per_month
-1
Organizations with a payment method receive $100/month in free CU credits and then pay overages at $0.0012059575 per 1,000 CU. No hard cap; scaled to budget.
System HTTP rate limit (no payment method) api_key
requests_per_period
-1
HTTP request rate limits exist per 5-minute window for organizations without a payment method. Specific numbers are tier-specific and set by Geomi admins; not publicly documented.
System HTTP rate limit (payment method attached) api_key
requests_per_period
-1
Higher default HTTP rate limits apply when a payment method is attached. Organizations may receive custom limit bumps from Geomi admins.

Policies

API Key Authentication
Obtain an API key from geomi.dev to authenticate requests with significantly higher limits than anonymous per-IP access. Pass key in request headers as documented.
Exponential Backoff on 429
On HTTP 429 responses, apply exponential backoff with jitter before retrying. Respect any Retry-After header value returned by the server.
Compute Unit Budgeting
Monitor CU consumption via the Geomi real-time dashboard. Set budget alerts to avoid unexpected service interruption at free-tier limits or unexpected overage charges.
Self-Hosting Option
For workloads requiring very high throughput, operators can self-host the Aptos fullnode and indexer to avoid shared rate limits entirely.
SDK Rate Limit Handling
The official Aptos TypeScript SDK automatically handles rate limits when accessing the Indexer API. Prefer SDK usage over raw HTTP for built-in retry logic.

Sources