Skip to content

Pricing

Usage is metered in CUs (Compute Units): each JSON-RPC method consumes a set number of CUs based on its weight.

Cache hits are always billed at 1 CU.

Methods not listed in the weight table are billed at 10 CU.

Every 1000 CU settles as 1 billing unit; the price per unit is still being finalized.

Resolution rule

Resolved in order: exact method match → the longest matching prefix rule ending in * → the default weight for anything else.

exact > longest prefix (pattern ending in *) > default

Settlement

Usage is aggregated per account over hourly periods; at the end of each period, that period's total CU is converted to billing units and charged:

floor(account CU per hourly period / 1000)

Balance & admission

The gateway checks balance against unsettled CU in real time and rejects new requests once it's exhausted:

block when balance - ceil(unsettled CU / 1000) <= 0

Full method weight table

Sorted by CU, lowest first. Rules ending in * match the longest matching prefix.

MethodCU
eth_blockNumber1
eth_chainId1
eth_getBlockByNumber5
eth_getBlockReceipts10
eth_getProof10
eth_call20
eth_createAccessList20
eth_estimateGas20
eth_simulateV120
eth_sendRawTransaction30
eth_getLogs50
debug_trace*prefix match200
Any other method10
Cache hit (any method)1

Allowed & denied methods

Allowed methods follow these prefix patterns:

eth_*net_*web3_*debug_trace*

The following methods are explicitly denied:

eth_newFiltereth_newBlockFiltereth_newPendingTransactionFiltereth_getFilterLogseth_getFilterChangeseth_uninstallFiltereth_subscribeeth_unsubscribe

Pricing & plans

Pricing and plans are coming soon — contact us now for a quote.

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 are cache hits billed?

A call that hits the cache never reaches the node, and is always billed at 1 CU.

How do I get an API key?

Self-serve console access isn't live yet — visit the Get API Key page and email us for manual onboarding.

View the JSON-RPC reference →