TriportRPC
DashboardDocs

Polygon RPC URL & node API — chain ID 137

Last updated:

Get API key Read the documentation

Network details

Polygon connection values
NetworkPolygon PoS mainnet
Chain ID137 (0x89)
CurrencyPOL
RPC URLhttps://triport.io/polygon
WebSocket URLwss://triport.io/ws/poly
Keyed URL for walletshttps://triport.io/r/<API_KEY>/polygon
Authenticationx-token: $TRIPORT_API_KEY (Authorization: Bearer also accepted), scope polygon:rpc

Need the values in a wallet or framework format? The Polygon chain config generates them for MetaMask, viem, ethers, Hardhat and Foundry.

What works today

Capabilities published as available — from the generated capability registry
CapabilityStatusMethods
JSON-RPC readsAvailable32 methods
WebSocket subscriptions (free+)AvailablenewPendingTransactions
WebSocket subscriptions (basic+)Availablelogs
WebSocket subscriptions (pro+)AvailablenewHeads, syncing

Reads cover the standard EVM surface — balances, code and storage, blocks and receipts, transactions, logs, gas and fee history, plus eth_getProof and the filter methods. All of them draw on one read budget: Polygon has no separate heavy category, so eth_getLogs is paced like any other read.

WebSocket subscriptions, by plan

wss://triport.io/ws/poly speaks the standard eth_subscribe / eth_unsubscribe wire shape, the same as Ethereum. Which subscription types a key may open depends on its plan: newPendingTransactions from the Free trial, logs from Basic, newHeads and syncing from Pro. Polygon-specific bor_subscribe* methods are not served on this channel.

Transaction submission is not sold here yet

eth_sendRawTransaction is routed (registry status: Limited), but acceptance of a valid transaction has not been re-verified end to end, so this page does not offer it. If you use it anyway, a submit response is not inclusion — check the receipt.

What this page does not sell

Bor validator methods: available on request, not self-serve. Anything that is not in the table above is not sold on this page — each method's page in the Polygon JSON-RPC reference carries its current status. We also publish no latency figures: the rate limits below are per-category RPS limits, not measured upstream capacity.

Limits and plans

Requests per second by plan — per-category RPS limits, not measured upstream capacity
CapabilityFree trial (7 days)BasicProBusinessEnterprise
Reads (polygon_read_rpc)1520100250no per-category cap
WebSocket subscriptionsnewPendingTransactions+ logs+ newHeads, syncingsame as Proall

Sustained rates carry a 2x burst. Plans: Basic $20, Pro $249, Business $499, Enterprise from $999 per month — a flat monthly price, no credits or overage: only the per-category RPS limits above. Free is a 7-day trial with a single key in the EU region, not a permanent plan. See Polygon limits.

Every plan with its limits on every network, and what a plan costs at its cap: RPC pricing.

Quickstart

# curl
curl https://triport.io/polygon \
  -H 'x-token: $TRIPORT_API_KEY' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# -> {"jsonrpc":"2.0","id":1,"result":"0x89"}

# viem
import { createPublicClient, http } from "viem";
import { polygon } from "viem/chains";
const client = createPublicClient({
  chain: polygon,
  transport: http("https://triport.io/r/<API_KEY>/polygon"),
});

# Hardhat / Foundry
networks: { polygon: { url: "https://triport.io/r/<API_KEY>/polygon", chainId: 137 } }
rpc_endpoints = { polygon = "https://triport.io/r/<API_KEY>/polygon" }

FAQ

What is the Polygon RPC URL?
https://triport.io/polygon for JSON-RPC over HTTPS and wss://triport.io/ws/poly for WebSocket subscriptions. Authenticate with the x-token header, or use the keyed URL https://triport.io/r/<API_KEY>/polygon where a wallet cannot send a custom header.
What is the Polygon chain ID?
137 (0x89 in hex) for Polygon PoS mainnet. eth_chainId on the Triport endpoint returns 0x89, and the gas token is POL. Standard EVM tooling — viem, ethers, Hardhat, Foundry, MetaMask — works against it.
Is there a free Polygon RPC endpoint?
There is a 7-day free trial with one key in the EU region: 15 read requests per second on Polygon, plus newPendingTransactions over WebSocket. After it, plans are flat monthly prices starting with Basic at $20.
Does Polygon RPC on Triport support WebSocket?
Yes, at wss://triport.io/ws/poly with eth_subscribe. newPendingTransactions is open from the trial, logs from Basic, newHeads and syncing from Pro. Polygon-specific bor_subscribe methods are not served on this channel.
Does Triport charge credits or compute units for Polygon calls?
No. Each plan is a flat monthly price with a requests-per-second budget per category, so an eth_getLogs call and an eth_blockNumber call cost the same: one request against the read budget.
Can I send Polygon transactions through Triport?
Not as a sold capability yet. eth_sendRawTransaction is routed, but acceptance of a valid transaction has not been re-verified end to end, so this page does not offer it. If you use it, a submit response is not inclusion — check the receipt.
What are the Polygon rate limits?
Reads 15/20/100/250 requests per second on the Free trial, Basic, Pro and Business, with a 2x burst. Enterprise has no per-category cap. These are per-category RPS limits, not measured upstream capacity.

Polygon read methods