What is the Polygon RPC URL?

The Polygon Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 137.

How do I add Polygon to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Polygon, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon, Chain ID: 137, Currency Symbol: POL, Block Explorer: https://polygonscan.com.

What is the difference between Polygon Mainnet and Polygon Amoy?

Polygon Mainnet (Chain ID 137) is the live production network. Polygon Amoy (Chain ID 80002) is the official testnet for development and testing before deploying to mainnet.

Why do public Polygon RPCs fail in production?

Public Polygon endpoints are shared infrastructure serving thousands of applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. For production applications, a dedicated provider is required.

What is the Polygon PoS chain?

Polygon PoS (Proof of Stake) is the main Polygon blockchain network, Chain ID 137. It is an EVM-compatible sidechain to Ethereum, using validators secured by the POL token. It periodically checkpoints state to Ethereum for security.

Does BoltRPC support WebSocket for Polygon?

Yes. BoltRPC provides WebSocket endpoints for Polygon at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/polygon. Use WebSocket for real-time event streaming: new blocks, pending transactions, contract event logs.

What happened to MATIC and what is POL?

POL replaced MATIC as the native token of the Polygon ecosystem in 2024 as part of the Polygon 2.0 upgrade. The gas token on Polygon PoS mainnet is now POL. The chain itself (Chain ID 137) and the RPC interface did not change.

Polygon RPC Endpoint

High-volume Polygon PoS workloads run on 2-second blocks. A dedicated endpoint keeps indexers, games and payment flows in sync, from $49/mo.

chain id · 137JSON-RPC 2.0WebSocketFull archiveDebug

Start free trial Contact sales

LIVE LATENCY

13ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/polygon

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

import { createPublicClient, http } from "viem";
import { polygon } from "viem/chains";

const client = createPublicClient({
  chain: polygon,
  transport: http("https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon"),
});

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect your dApp, bot, or protocol to Polygon Mainnet with BoltRPC. For DeFi bots making hundreds of RPC calls per minute, predictable request-unit pricing eliminates the cost unpredictability of opaque compute-weighted billing models.

Chain at a Glance


Chain ID	137
Protocol	PoS sidechain
Block time	~2 s
Native token	POL
Finality	Ethereum L1 checkpoints (~30 min)
EVM compatible	Yes

What Polygon is Built For

Polygon PoS is the primary EVM sidechain for high-volume, low-fee activity. It serves a broad ecosystem: gaming protocols, NFT marketplaces, enterprise blockchain projects and DeFi applications that need Ethereum compatibility without Ethereum gas costs. Chainlink oracle networks run on Polygon for price feeds and data delivery. POL replaced MATIC as the native token in 2024. The combination of 2-second blocks, low fees and EVM compatibility makes Polygon attractive for applications that need to process many transactions, which in turn requires an RPC provider that can handle sustained high request volumes without throttling.

Common Use Cases on Polygon

High-frequency DeFi bots Polygon’s low fees and 2-second blocks make it the chain of choice for DeFi bots that need to execute dozens of trades per minute. Yield aggregators poll lending rates across Aave, QuickSwap and other protocols continuously, calling eth_call on multiple contract addresses to find arbitrage windows. The volume of calls per session is an order of magnitude higher than on Ethereum mainnet, which is exactly why predictable request-unit RPC pricing matters here.

NFT marketplace backends NFT platforms on Polygon query ownership, metadata and transfer history at scale. A marketplace listing page may require dozens of eth_call and eth_getLogs requests to build a single user view. During active collection drops, this read load spikes sharply. Dedicated RPC handles the burst without dropping connections.

Gaming item ownership and in-game economies Blockchain games use Polygon for in-game assets: weapons, land parcels, player inventory. Backend systems query item ownership and player balances before every game action, generating sustained read traffic. WebSocket subscriptions let game servers react to on-chain trades and transfers instantly rather than polling every block.

Chainlink oracle integrations Chainlink oracle networks operate on Polygon to deliver price feeds and data to DeFi protocols. Infrastructure supporting Chainlink on Polygon requires reliable RPC access for both data submission and verification. BoltRPC’s parent company Matrixed.Link operates Chainlink oracle infrastructure, making it a natural fit for teams building Chainlink-adjacent workflows.

Built for teams that ship on Polygon.

DeFi bot economics work differently on request-unit pricing

Polygon DeFi bots often make hundreds of RPC calls per minute: polling prices, checking liquidity, monitoring positions. On opaque compute-weighted billing, eth_getLogs and eth_call accumulate cost fast at that frequency. BoltRPC prices every method with a fixed, published RU weight, so bot operators can size a plan to their call mix instead of facing surprise multipliers. Your monthly bill is predictable.

High-frequency chain, high RPC demands

Polygon processes millions of transactions per day with 2-second block times. At that volume, public Polygon RPCs hit rate limits and drop connections under load. Production applications need a dedicated provider.

Consistent response times under load

BoltRPC delivers consistent response times regardless of Polygon network congestion. No degradation during peak periods.

Full EVM compatibility for quick migration

Polygon is EVM-compatible. Any Ethereum contract deploys to Polygon without modification. Switch the RPC endpoint and update the Chain ID.

WebSocket for event-driven DeFi

Subscribe to DEX events, liquidation triggers, and oracle updates via WebSocket. Event-driven architecture reduces unnecessary polling and RPC usage.

Testnet coverage included

BoltRPC also supports Polygon Amoy testnet, Polygon's current testnet. One provider covers your full development and production workflow.

Full JSON-RPC coverage.

Every standard Polygon method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD5

eth_calleth_getLogseth_sendRawTransactioneth_getTransactionReceipteth_getBalance

Polygon, explained.

Common questions about connecting to Polygon over BoltRPC.

Ask a question →Read the docs

: The Polygon Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 137.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Polygon, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/polygon, Chain ID: 137, Currency Symbol: POL, Block Explorer: https://polygonscan.com.
: Polygon Mainnet (Chain ID 137) is the live production network where real transactions happen. Polygon Amoy (Chain ID 80002) is the official testnet, use it for development and testing before deploying to mainnet. BoltRPC supports both networks.
: Public Polygon endpoints are shared infrastructure serving thousands of applications simultaneously. Under load they rate-limit requests, return stale block data, and drop WebSocket connections. For production applications, a dedicated provider with consistent response times is required.
: Polygon PoS (Proof of Stake) is the main Polygon blockchain network, Chain ID 137. It is an EVM-compatible sidechain to Ethereum, using a set of validators secured by the POL token. When people refer to "Polygon", they typically mean Polygon PoS. It periodically checkpoints state to Ethereum for added security.
: Yes. BoltRPC provides WebSocket endpoints for Polygon at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/polygon. Use WebSocket when you need real-time event streaming: new blocks, pending transactions, contract event logs.
: POL replaced MATIC as the native token of the Polygon ecosystem in 2024 as part of the Polygon 2.0 upgrade. On Polygon PoS mainnet, the gas token is now POL. Existing MATIC holders could migrate to POL. The chain itself (Chain ID 137) and the RPC interface did not change.

Ship on Polygon this week.

An API key in under 60 seconds, Polygon plus 23 other chains, and a team that answers when you write.

Start free trial View pricing