Read and submit
Query chain data and send signed transactions with compatible JSON-RPC methods.
Multi-chain infrastructure
Polygon RPC nodes.
Ready for your next build.
Build on Polygon PoS with RPC, WebSockets, gRPC and archival access. Choose a straightforward monthly capacity plan and use the tools you already know.
POLYGON / DEVELOPER ENDPOINT
PolygonYour application, connected.JSON-RPCRead & submit
WebSocketsSubscribe to updates
ArchiveHistorical queries
Use your preferred EVM-compatible SDK.
25 RPSFree starting tier
1,000 RPSTop shared tier
HTTP + WSFamiliar interfaces
What you can build
Polygon RPC infrastructure.
A familiar foundation.
Connect, query and subscribe through the interfaces your tools expect, with dedicated nodes and round-the-clock support when you go to production.
Follow the chain
Subscribe through WebSockets to keep your application in step with updates.
Work with history
Archival access is included across these plans. Confirm the methods your application needs.
gRPC on every plan
Every Polygon plan includes gRPC beside JSON-RPC and WebSockets, so backend services can use the protocol they prefer.
Dedicated Polygon nodes
Your own node on isolated hardware with guaranteed resources and custom configuration. No shared infrastructure, no noisy neighbors.
99.99% uptime, 24/7 support
A 99.99% uptime SLA, with blockchain-native engineers available around the clock on Discord, Telegram and email.
Capacity you can understand
Polygon RPC pricing.
Start free. Scale as you build.
Monthly pricing. Choose capacity around your workload; confirm availability and final settings before ordering.
Free
$0/month
25requests / second
- JSON-RPC access
- WebSocket subscriptions
- Archival data
- gRPC included
Starter
$49/month
100requests / second
- JSON-RPC access
- WebSocket subscriptions
- Archival data
- gRPC included
Growth
$149/month
300requests / second
- JSON-RPC access
- WebSocket subscriptions
- Archival data
- gRPC included
Pro
$299/month
600requests / second
- JSON-RPC access
- WebSocket subscriptions
- Archival data
- gRPC included
Performance
$499/month
1,000requests / second
- JSON-RPC access
- WebSocket subscriptions
- Archival data
- gRPC included
Polygon also includes gRPC across these tiers. Plans run in Amsterdam.
Need a dedicated Polygon node?
Run your own Polygon node on isolated hardware, with throughput, configuration and SLA terms sized to your workload. Pricing is quoted per deployment.
- Dedicated hardware, no shared resources
- Unmetered usage
- Custom configuration and SLA terms
- Priority engineering support
Why OrbitFlare
Beyond the public Polygon RPC endpoint.
Free public endpoints are built for wallet connectivity and testing. Production applications need guaranteed throughput, archival reads and an SLA to stand behind them.
| Feature | OrbitFlare | Public RPC |
|---|---|---|
| Requests per second | 25 to 1,000 by plan, or a dedicated node | Rate limited, unspecified |
| Guaranteed capacity | Per-plan guarantee | Best effort |
| Archival data | Included on every plan | Rarely available |
| WebSocket subscriptions | Included on every plan | Limited |
| Uptime SLA | 99.99% | None |
| Support | 24/7 engineers on Discord, Telegram and email | None |
| Dedicated nodes | Available on request | Not available |
Developer experience
A Polygon RPC endpoint.
The tools you already use.
Connect viem, ethers.js, web3.js, Foundry or Hardhat to your issued endpoint. Keep keys out of browser bundles and public repositories.
app.ts
import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider(
process.env.YOUR_RPC_ENDPOINT
);
const block = await provider.getBlockNumber();Example only · replace placeholders
Choose a plan
Start with the request capacity your application needs.
Get your endpoint
Use your issued endpoint and authentication settings.
Test your workload
Check required methods, subscriptions and burst traffic before rollout.
Chain settings
Polygon PoS network details
Everything a wallet or client needs to reach Polygon PoS. These plans cover Polygon PoS; we do not serve Polygon zkEVM.
| Network name | Polygon Mainnet |
|---|---|
| Chain ID | 137 |
| Currency symbol | POL (formerly MATIC) |
| RPC URL | Your OrbitFlare Polygon endpoint |
| Interfaces | HTTPS JSON-RPC, WSS subscriptions and gRPC |
| Block explorer | https://polygonscan.com |
| Amoy testnet chain ID | 80002 |
| OrbitFlare locations | Amsterdam |
Polygon PoS is EVM-compatible: ethers.js, viem, web3.js, Foundry and Hardhat all work once the chain ID is set to 137.
Read the Polygon docsBefore you connect
Polygon PoS RPC node FAQs
What makes OrbitFlare Polygon RPCs different?
Our Polygon RPC infrastructure is built for production workloads with clear tiered performance. Plans start at 25 requests per second and scale to 1,000, and every plan includes JSON-RPC, WebSockets, gRPC and archival data.
What is Polygon?
Polygon PoS is an EVM-compatible scaling network for Ethereum, offering fast and low-cost transactions. It is widely used for DeFi, gaming, NFTs and enterprise blockchain applications. Polygon RPC nodes give your application access to the network for reading chain data and broadcasting transactions.
What performance can I expect?
Throughput is tiered by plan, in requests per second: Free 25, Starter 100, Growth 300, Pro 600 and Performance 1,000. You can upgrade as your application traffic grows.
What kind of applications can use Polygon RPCs?
Our Polygon RPCs suit DeFi protocols (AMMs, lending, yield), gaming and metaverse applications, NFT marketplaces and minting platforms, bridge protocols, trading bots and any EVM-compatible application that needs reliable Polygon access.
Is there a free Polygon RPC plan?
Yes. OrbitFlare offers a free Polygon plan with 25 requests per second, and you can upgrade to a higher tier any time for more throughput.
What is a Polygon RPC URL and where do I get one?
A Polygon RPC URL is the HTTPS (or WSS) endpoint your wallet, dApp or script sends JSON-RPC requests to in order to read Polygon state and submit transactions. Public endpoints are shared and rate limited. An OrbitFlare Polygon RPC URL is keyed to your account and includes WebSockets, gRPC and archival data on every plan, starting with a free tier.
What is the Polygon mainnet chain ID and network configuration?
Polygon PoS mainnet uses chain ID 137, the native token is POL (formerly MATIC) and the block explorer is polygonscan.com. To add it to a wallet, enter your OrbitFlare Polygon RPC URL as the network RPC, chain ID 137 and currency symbol POL. The Amoy testnet uses chain ID 80002.
Can I use familiar Ethereum tooling?
Yes. Polygon PoS is EVM-compatible, so ethers.js, viem, web3.js, Foundry and Hardhat work with your OrbitFlare endpoint. Keep network and chain configuration explicit (chain ID 137) and test the methods your application requires.
Does OrbitFlare support Polygon archive and trace methods?
Yes. Archival state and WebSocket subscriptions are included on every Polygon plan, so historical balance and storage queries at old blocks work without a separate archive tier. Debug and trace methods are available on paid plans and on dedicated instances.
What support is available?
We provide 24/7 technical support from engineers who understand blockchain infrastructure. You can reach us on Discord, Telegram or email.
How do I get started with a dedicated Polygon instance?
Open a ticket or contact us on Discord or Telegram with your expected sustained and burst traffic, method mix and deployment requirements. We will size and provision a dedicated Polygon instance for you.
Code. Build. Stream. Without Limits.
Start building on Polygon.
Bring your next Polygon idea online: choose capacity, connect your client and ship.