RPC operator referenceHTTPS · JSON-RPC 2.0

Polygon PoS RPC endpoint

Polygon PoS (chain ID 137) is served over HTTPS POST JSON-RPC 2.0. Full and archive nodes back the endpoint, supporting standard EVM methods, historical state, debug_* methods. Every plan includes Polygon PoS, including Free.

Network information

Network	Polygon PoS
Chain ID	137
Endpoint	`https://rpc.solidrpc.io/YOUR_API_KEY/evm/137`
Type	Mainnet · L1
Native currency	POL
Node types	Full + Archive
Methods	standard, debug
Protocol	HTTPS JSON-RPC 2.0 (no WebSocket)

Testing first? Polygon PoS has a testnet on SolidRPC: Polygon Amoy.

Quickstart

Fetch the latest Polygon PoS block number. Replace YOUR_API_KEY with a key from the dashboard, new accounts start on the Free plan, no card required (see getting started):

Request example

curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/137 \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Archive access and tracing

There is no separate archive endpoint for Polygon PoS; historical queries route to archive nodes automatically by block age, at no surcharge.

The debug_* tracing namespace is available:

Request example

curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/137 \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xTRANSACTION_HASH",{"tracer":"callTracer"}],"id":1}'

Parity-style trace_* methods are not available on this chain; use debug_traceTransaction and debug_traceBlockByNumber instead.

Details on archive nodes and tracing.

Limits and errors

Quotas and rate limits are account-wide, not per-chain. Method calls to Polygon PoS draw from the same response-unit quota and rate limit as every other network. Error bodies are identical everywhere; see the error reference.

All networks