Node RPCs

Introduction

Node RPC is Gelato's high-performance solution for accessing rollup networks without running your own nodes. It offers developers reliable, scalable access to Gelato-supported chains, enabling efficient dApp development and deployment.

Understanding Compute Units (CUs)

What are Compute Units

Compute Units (CUs) measure the computational resources consumed by your API calls. They provide a standardized way to quantify usage across different types of requests.

Why use Compute Units?

CUs ensure transparent and fair pricing. Instead of flat rates, you pay based on the actual computational cost of your requests. This approach prevents overpaying for simple queries while accurately reflecting resource usage for complex operations.

CU Costs for Common Calls

net_version	0
eth_chainId	0
eth_syncing	0
eth_protocolVersion	0
net_listening	0
eth_uninstallFilter	10
eth_accounts	10
eth_blockNumber	10
eth_subscribe	10
eth_unsubscribe	10
eth_feeHistory	10
eth_maxPriorityFeePerGas	10
eth_createAccessList	10
eth_getTransactionReceipt	15
eth_getUncleByBlockHashAndIndex	15
eth_getUncleByBlockNumberAndIndex	15
eth_getTransactionByBlockHashAndIndex	15
eth_getTransactionByBlockNumberAndIndex	15
eth_getUncleCountByBlockHash	15
eth_getUncleCountByBlockNumber	15
web3_clientVersion	15
web3_sha3	15
eth_getBlockByNumber	16
eth_getStorageAt	17
eth_getTransactionByHash	17
eth_gasPrice	19
eth_getBalance	19
eth_getCode	19
eth_getFilterChanges	20
eth_newBlockFilter	20
eth_newFilter	20
eth_newPendingTransactionFilter	20
eth_getBlockTransactionCountByHash	20
eth_getBlockTransactionCountByNumber	20
eth_getProof	21
eth_getBlockByHash	21
erigon_forks	24
erigon_getHeaderByHash	24
erigon_getHeaderByNumber	24
erigon_getLogsByHash	24
erigon_issuance	24
eth_getTransactionCount	26
eth_call	26
eth_getFilterLogs	75
eth_getLogs	75
eth_estimateGas	87
eth_sendRawTransaction	250
eth_getBlockReceipts	500
batch	CU of method # of times the method is called

Pricing and Plans

Plan Overview

Free

• 500M CUs/month no autoscale

• 1 API key

• 300 CU/s

Pro

• $50/month

• 1B CUs/month included, then autoscale

• 20 API keys

• Basic support

• 1000 CU/s

Enterprise

• Custom pricing

• Customised CU allocation

• Unlimited API keys

• Priority support

• Autoscale

Scaling and Usage

• Automatic scaling: $0.10/1M CUs after exceeding the base CU limit

• Example: On the Pro plan, after using 1.0B CUs, each additional 1M CUs costs $0.10

Using Node RPC

API Key Usage

• Public endpoints: Available but rate-limited

• Authenticated access: Create an account and use an API key for optimal performance

CU Allocation

CUs are consumed at the Gelato organization level. Your base limit applies across all networks and RPC keys within your organization.

FAQ

Q: Can I use Node RPC without an RPC key? A: Yes, but it's rate-limited. We recommend using an RPC key for the best experience.

Q: How are CUs allocated across my organization? A: CUs are pooled at the organization level and can be used across multiple projects and RPC keys.

Additional Terms

• CUs don't roll over between billing cycles

• CU costs for specific methods may change with 30 days notice

• Accounts inactive for 90 days may be suspended

• Enterprise accounts include a 99.9% uptime SLA