Polygon RPC Endpoints, API & Dedicated Nodes

Bringing the world to Ethereum

Chain ID137

CurrencyPOL

Use Polygon RPC endpoints for dApps, wallets, DeFi, analytics, archive queries, trace debugging, and dedicated node infrastructure.

Bringing the world to Ethereum

Create RPC EndpointDeploy Dedicated Node

Polygon RPC Endpoint

The below example uses the public API endpoint*. This endpoint is only suitable for testing. To avoid rate limiting and service interruption, sign up now to get your own API key.

Example CURL

curl -H 'content-type:application/json' -d '{"id": 1, "jsonrpc": "2.0", "method": "eth_blockNumber"}' 'https://polygon.api.onfinality.io/public'

curl -H 'content-type:application/json' -d '{"id": 1, "jsonrpc": "2.0", "method": "eth_blockNumber"}' 'https://polygon.api.onfinality.io/public'

HTTPs

https://polygon.api.onfinality.io/public

https://polygon.api.onfinality.io/public

Websocket

wss://polygon.api.onfinality.io/public-ws

wss://polygon.api.onfinality.io/public-ws

* The public endpoint is rate limited

RPC API Service

RPC API Features

ArchiveTrace

RPC Regions

N.Virginia

Dedicated Nodes

Node Type

Full

Node Endpoints

JSON-RPCWebSocketsMetrics

PRICING

Calculate Your Costs

Only pay for what you need.

Polygon RPC API Service

Polygon Dedicated Nodes

Monthly Response Units

Million Standard Requests

0100M200M300M400M

Total Cost

$49/ month

Recommended Plan: GROWTH

Continue with this plan

Build on Polygon with OnFinality RPC endpoints and dedicated node options for apps that need reliable access to Polygon PoS. Polygon is an EVM-compatible network, so teams can use familiar Ethereum tooling while benefiting from lower-cost transactions and faster app workflows.

Polygon RPC use cases

Polygon RPC endpoints let applications read balances, call contracts, submit transactions, query logs, and monitor receipts. The endpoint becomes part of the user experience for wallets, games, DeFi products, NFT tools, trading bots, analytics jobs, and backend services.

Common workloads include:

User-facing dApps that need responsive reads and transaction status.
Backend jobs that query logs, receipts, and contract state.
Analytics or compliance workflows that need archive access.
Debugging workflows that use trace data where supported.

OnFinality Polygon RPC features

Network: Polygon Mainnet, Chain ID 137
Protocol: EVM JSON-RPC
Transport: HTTP and WebSocket
Advanced access: Archive and trace support available
Dedicated nodes: Dedicated Polygon node options for production workloads

What to test first

Start with eth_blockNumber, then test eth_call, eth_getLogs, transaction submission, WebSocket subscriptions, and the exact retry behavior your app uses under load.

Polygon mainnet and Amoy testing

Use Polygon Amoy for staging contract deployments and wallet flows before moving traffic to mainnet. Keep your testnet and mainnet endpoint strategy close enough that release checks catch real integration problems.

Next steps: