Polygon Amoy RPC: Complete Guide to Endpoints, Providers, and Best Practices

What is Polygon Amoy?

Polygon Amoy is the official testnet for Polygon PoS, launched in January 2024 to replace the deprecated Mumbai testnet. It uses Ethereum Sepolia as its root (L1) chain, ensuring long-term sustainability as Goerli is phased out. Developers can test smart contracts, dApps, and infrastructure in a low-stakes environment with access to essential validators, faucets, and tooling.

Key network details: Chain ID 80002 (0x13882), native token POL, and block explorer at https://amoy.polygonscan.com. Testnet tokens are available from the official Polygon faucet.

• Network Name: Polygon Amoy
• Parent Chain: Ethereum Sepolia
• Chain ID: 80002
• Gas Token: POL
• Block Explorer: https://amoy.polygonscan.com
• RPC Endpoint: https://polygon-amoy.drpc.org (example)
• WSS Endpoint: wss://polygon-amoy.drpc.org (example)

Polygon RPC decision checklist

Use this checklist to turn the Polygon RPC question into a practical infrastructure decision instead of a generic provider comparison.

Shortlist providers only after you know which methods, environments, traffic patterns, and support expectations matter to the workload.

• List the exact RPC methods, chains, and environments your app will call.
• Test with the same request pattern your frontend, backend, bot, dashboard, or indexer will use.
• Check whether archive, trace, WebSocket, testnet, analytics, or dedicated-node access is actually required.
• Review pricing, usage visibility, and upgrade paths before moving sustained traffic.

Polygon Amoy RPC Endpoints

Multiple RPC endpoints are available for Polygon Amoy, both public and private. Public endpoints are free but often have rate limits and no clearer infrastructure expectations. Paid providers offer higher rate limits, dedicated nodes, and SLAs suitable for production testing.

Below is a list of commonly used Polygon Amoy RPC endpoints. Always verify the latest endpoint status from the provider's documentation.

How to Choose an RPC Provider for Polygon Amoy

Selecting the right RPC provider depends on your testing requirements. For light testing, a public endpoint may suffice. For consistent performance, consider a dedicated node or a paid plan with rate limit documents.

Key factors to evaluate: rate limits, support and monitoring options, geographic distribution, WebSocket support, and pricing. OnFinality offers both a public endpoint and dedicated nodes for Polygon Amoy, giving you flexibility as your testing needs grow.

• Rate Limits: Public endpoints typically allow 10-100 requests per second; paid plans offer higher limits.
• support and monitoring options: Paid providers often documents documented availability availability; public endpoints have no support terms.
• WebSocket Support: Essential for real-time applications; verify WSS endpoint availability.
• Geographic Distribution: Global nodes reduce latency; check provider's node locations.
• Pricing: Compare free tiers and paid plans; some providers charge per request or monthly.

How to Connect to Polygon Amoy RPC

Connecting to Polygon Amoy is straightforward. You can use the RPC endpoint in your dApp, wallet, or directly via curl. Below is an example using curl to check the latest block number.

• Using curl: curl -X POST https://polygon-amoy.drpc.org -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
• Using Web3.js: const web3 = new Web3('https://polygon-amoy.drpc.org'); web3.eth.getBlockNumber().then(console.log);
• Using ethers.js: const provider = new ethers.providers.JsonRpcProvider('https://polygon-amoy.drpc.org'); provider.getBlockNumber().then(console.log);
• Adding to MetaMask: Network Name: Polygon Amoy, RPC URL: https://polygon-amoy.drpc.org, Chain ID: 80002, Currency Symbol: POL, Block Explorer: https://amoy.polygonscan.com

Common Issues and Troubleshooting

Developers may encounter issues when connecting to Polygon Amoy RPC. Below are common problems and solutions.

• Rate Limiting: If you receive '429 Too Many Requests', reduce request frequency or switch to a paid provider with higher limits.
• Incorrect Chain ID: Ensure your wallet or dApp uses Chain ID 80002 (0x13882). Using the wrong chain ID will cause transaction failures.
• Stale Endpoint: Public endpoints may go offline or become slow. Always verify endpoint status from the provider's status page.
• WebSocket Disconnections: Use reconnection logic in your code to handle temporary disconnections.
• Transaction Not Mined: Check gas price and nonce; Amoy uses POL as gas token. Use the gas station at https://gasstation.polygon.technology/.

Polygon Amoy vs. Mumbai: Key Differences

Amoy replaces Mumbai as the primary testnet for Polygon PoS. The main difference is the root chain: Amoy uses Sepolia, while Mumbai used Goerli. As Goerli is deprecated, Mumbai is no longer supported. Developers should migrate to Amoy.

Best Practices for Using Polygon Amoy RPC

Follow these best practices to ensure a smooth development experience on Polygon Amoy.

• Use a dedicated node or paid RPC provider for consistent performance during heavy testing.
• Implement fallback endpoints in your dApp to handle provider outages.
• Monitor your RPC usage to avoid hitting rate limits unexpectedly.
• Keep your Web3 libraries updated to support the latest JSON-RPC methods.
• Test thoroughly on Amoy before deploying to Polygon mainnet.

Frequently Asked Questions