Connect EVM applications to C-Chain; use the separate P-Chain API for validator and staking data.
Use OnFinality's Avalanche C-Chain RPC at https://avalanche.api.onfinality.io/public/ext/bc/C/rpc for EVM applications on chain ID 43114. Validator and staking queries use a separate P-Chain endpoint.
Public endpoint rate limit: 5 req/sec
curl -H 'Content-Type: application/json' -d '{"id":1,"jsonrpc":"2.0","method":"eth_blockNumber","params":[]}' 'https://avalanche.api.onfinality.io/public/ext/bc/C/rpc'https://avalanche.api.onfinality.io/public/ext/bc/C/rpcUse OnFinality Avalanche C-Chain RPC with chain ID 43114 and JSON-RPC examples. Find the separate P-Chain API for staking data and choose your app access plan.
curl 'https://avalanche.api.onfinality.io/public/ext/bc/C/rpc' \
-H 'Content-Type: application/json' \
--data '{"id":1,"jsonrpc":"2.0","method":"eth_blockNumber","params":[]}'Use the interface and request shown above for an initial check, then test the methods and traffic pattern your application actually needs.
Choose a shared RPC plan by response-unit allowance and peak throughput. Method weights and network-specific availability still apply.
Plan figures checked 8 November 2026. RU are not always raw requests; WebSocket responses also count toward limits. Check the current pricing and this network's method documentation. Node charges and applicable taxes are additional.
Use C-Chain for EVM wallets, Solidity contracts, balances and transaction receipts. Use P-Chain for validator and staking data. These APIs use different URL paths and methods.
| API | HTTPS endpoint | First method to check |
|---|---|---|
| C-Chain EVM RPC | https://avalanche.api.onfinality.io/public/ext/bc/C/rpc | eth_chainId, then eth_blockNumber |
| P-Chain API | https://avalanche.api.onfinality.io/public/ext/bc/P | platform.getHeight |
C-Chain mainnet uses chain ID 43114 (0xa86a) and AVAX for gas. The P-Chain URL is not an EVM wallet RPC URL; do not use it for eth_* calls or wallet network configuration.
The quick-start examples above use eth_blockNumber on C-Chain. Run eth_chainId against the same URL and confirm 0xa86a before querying contracts or submitting signed transactions.
C-Chain chain ID and block reads were verified on October 21, 2026. Endpoint availability and block height change over time.
Create an OnFinality account, select Avalanche and copy the endpoint for the chain your application uses. Replace the anonymous public URL with your authenticated URL and keep its chain path intact. Review RPC plans for request limits and usage analytics.
Test the exact historical queries or trace methods your workload needs on your selected plan. The public connection details here describe HTTPS access; a P-Chain HTTPS address is not a WebSocket subscription URL.
eth_call, balances, signed transactions and receipts.platform.* methods.Refer to the Avalanche developer documentation for C-Chain method semantics, and the Avalanche RPC guide for provider selection.
Plan access around the requests, operational requirements and release workflow your application needs.
Start with a connection check, then validate the reads, transactions or data workflows required by your application.
Review method-specific limits, plan allowances and usage before increasing traffic. Different methods can consume different response units.
Use your real client region and request pattern when evaluating latency, retries and service availability.
OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.
Get StartedBuild and scale blockchain applications with reliable RPC, indexing, and data infrastructure from OnFinality.
Get the latest product updates, technical insights, and key announcements delivered straight to your inbox.
Ethereum
Solana
Polygon
Base
Arbitrum
BNB Chain
Polkadot
Optimism