Pricing
Usage is metered in CUs (Compute Units): each JSON-RPC method consumes a set number of CUs based on its weight. Usage is totaled across all chains, JSON-RPC and Data API combined.
JSON-RPC methods not listed in the weight table are billed at 10 CU.
Every 1000 CU settles as 1 billing unit.
Resolution rule
Resolved in order: exact method match → the longest matching prefix rule ending in * → the default weight for anything else.
Settlement
Usage is charged per account per hourly period, rounded down to whole billing units (1 unit = 1000 CU), with the remainder carrying over to the next period (across periods the total charged is floor(total CU / 1000)); settlement runs about 15 minutes after the period ends. For example: 508 CU carried over + 2557 CU consumed = 3065 CU charges 3 billing units, with 65 CU carried over.
Balance & admission
Each request is checked against your balance in real time, including usage not yet billed. Once your balance runs out, new requests are rejected with HTTP 402.
Full method weight table
Sorted by CU, lowest first. Rules ending in * match the longest matching prefix.
| Method | CU | Per 1M calls (USD) |
|---|---|---|
| eth_blockNumber | 1 | $0.1 |
| eth_chainId | 1 | $0.1 |
| eth_getBlockByNumber | 5 | $0.5 |
| eth_getBlockReceipts | 10 | $1 |
| eth_getProof | 10 | $1 |
| eth_call | 15 | $1.5 |
| eth_createAccessList | 20 | $2 |
| eth_estimateGas | 20 | $2 |
| eth_simulateV1 | 20 | $2 |
| eth_getLogs | 30 | $3 |
| eth_sendRawTransaction | 30 | $3 |
| debug_trace*prefix match | 100 | $10 |
| Any other method | 10 | $1 |
Data API operations
| Method | CU | Per 1M calls (USD) |
|---|---|---|
| data.chains | 1 | $0.1 |
| data.status_freshness | 1 | $0.1 |
| data.block | 5 | $0.5 |
| data.block_by_hash | 5 | $0.5 |
| data.nft | 5 | $0.5 |
| data.token | 5 | $0.5 |
| data.transaction | 5 | $0.5 |
| data.block_transactions | 10 | $1 |
| data.tokens_batch | 10 | $1 |
| data.dex_prices | 15 | $1.5 |
| data.stock | 15 | $1.5 |
| data.stocks | 15 | $1.5 |
| data.address_balances | 25 | $2.5 |
| data.address_transactions | 25 | $2.5 |
| data.address_transfers | 25 | $2.5 |
| data.dex_swaps | 25 | $2.5 |
| data.nfts_by_owner | 25 | $2.5 |
| data.token_holders | 25 | $2.5 |
| data.token_transfers | 25 | $2.5 |
| data.block_traces | 200 | $20 |
| data.transaction_trace | 200 | $20 |
Chain-specific operations that are unavailable (e.g. unsupported chain or outside trace coverage) return HTTP 422 and are not billed.
Allowed & denied methods
Free plan
Includes 30,000,000 CU sign-up bonus. Each 30-day cycle starts on first billed usage and automatically refills up to 30,000,000 CU at the end of the period (no accumulation; granted credits are not clawed back, except for credits obtained in violation, see Terms of Service). All keys share an average of 5 calls per second, and short bursts are allowed. Make a paid top-up at any time to remove the call rate limit while keeping all remaining balance.
No credit card required — sign up instantly with GitHub, Google, or your wallet.
Your first paid top-up permanently upgrades the account and removes the per-second call limit.
Pricing & plans
Pay-as-you-go; 1 USD = 10,000 billing units (= 10,000,000 CU); minimum top-up is $10. Supported currencies: USD, USDT, USDC. Contact us to top up; your balance is credited once payment is confirmed.
FAQ
What is a CU?
A CU (Compute Unit) measures the resources a call consumes: different JSON-RPC methods consume different amounts of CU based on their weight — a higher weight means more load on the node.
How do I get an API key?
Click "Get an API key" and log in with GitHub, Google or an Ethereum wallet to create your account, then create a key in the console.
Which chains does one API key work on?
One API key works on all supported chains for JSON-RPC, and for the Data API on chains where it is available. Keys belong to your account, not to a specific chain. Prices follow your plan configuration — see the console and the Pricing page for details.
What is included in the Free Plan?
New accounts receive 30,000,000 Compute Units (CU) upon sign-up. When you make your first billed request, a 30-day usage window begins. When the window ends, your balance is automatically refilled up to 30,000,000 CU to guarantee your allowance for the next period. Unused credits never expire and are not clawed back (except credits obtained in violation of the Terms of Service), but they do not accumulate beyond 30,000,000 CU.
What are the rate limits on the Free Plan?
The Free Plan allows on average 5 calls per second across all API keys under the account, short bursts allowed (each call in a batch counts as 1 call). Each API key also has its own CU-per-second limit, shown in the Rate limit column of the API key list in the console.
What happens if I exhaust my free credits before the window ends?
If your balance is exhausted mid-window, requests will receive HTTP 402 (Insufficient Balance) until the current 30-day window ends and your balance is refilled to 30,000,000 CU, or until you add paid credits.
How do I upgrade to the Paid Plan?
Making your first paid top-up permanently upgrades your account to the Paid Plan. The average-rate limit of 5 calls per second is removed immediately, and any remaining free credits are merged directly into your paid balance. Paid accounts no longer receive periodic free refills.