What is the Polygon Amoy RPC URL?

The Polygon Amoy Testnet RPC URL with BoltRPC is https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY. Replace YOUR_API_KEY with your API key from trial.boltrpc.io. The chain ID is 80002.

What replaced Polygon Mumbai testnet?

Polygon Amoy replaced Mumbai as the official Polygon PoS testnet in 2024. Mumbai was deprecated and is no longer supported. Migrate to Amoy - it mirrors the current Polygon Mainnet stack.

How do I get test MATIC for Polygon Amoy?

Use the official Polygon Amoy faucet at faucet.polygon.technology. You will need a small amount of Sepolia ETH to request test tokens. Tokens are free and only valid on the Amoy testnet.

How do I add Polygon Amoy to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Polygon Amoy, RPC URL: https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY, Chain ID: 80002, Currency Symbol: MATIC, Block Explorer: https://amoy.polygonscan.com.

Why use a paid RPC provider for a testnet?

Public testnet RPCs drop connections during congestion, return stale data, and impose strict rate limits. For production development workflows with CI/CD pipelines, a reliable testnet endpoint saves significant debugging time.

What is the difference between Amoy and Mumbai?

Amoy is the current official Polygon PoS testnet, replacing Mumbai in 2024. Mumbai was deprecated as it ran an older Polygon stack. Amoy mirrors the current Polygon Mainnet configuration including the POL token upgrade.

Can I use the same API key for Amoy and Polygon mainnet?

Yes. BoltRPC uses one API key across all supported networks. Your Amoy URL uses polygon-amoy as the network slug and your mainnet URL uses polygon. Same key, same endpoint format, just a different slug.

Polygon Amoy Testnet RPC Endpoint

Quick connect

Your endpoint, ready in one line.

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

HTTPS

https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY

WebSocket

wss://eu.endpoints.matrixed.link/ws/polygon-amoy?auth=YOUR_API_KEY

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

Connect

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://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY"
);

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

const client = createPublicClient({
  chain: polygonAmoy,
  transport: http("https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY"),
});

Why BoltRPC

Built for teams that ship on Polygon.

Testnet parity with your mainnet setup

BoltRPC's Polygon Amoy endpoint uses the same format, the same API key, and the same infrastructure quality as the Polygon mainnet endpoint. Switching from testnet to mainnet means changing one line in your configuration. No separate accounts, no different auth patterns, no surprises.

Reliable testnet infrastructure for serious development

Polygon Amoy replaced Mumbai as the official Polygon testnet in 2024. Public testnet RPCs are notoriously unreliable: rate limits, resets, downtime during congestion. BoltRPC provides consistent testnet access for workflows that cannot afford a flaky connection.

Stable CI/CD pipelines

A flaky testnet endpoint breaks automated testing and deployment pipelines. BoltRPC gives your Amoy workflows the same stability as your mainnet setup. Integration tests that depend on RPC connectivity should not fail because the public testnet endpoint is congested.

Full EVM compatibility

Polygon Amoy mirrors Polygon PoS exactly. Code that works on Amoy deploys to mainnet without changes.

WebSocket for testnet event-driven testing

Subscribe to Amoy events via WebSocket. Useful for integration tests that need to react to transaction events in real time rather than polling.

One provider for Polygon mainnet and testnet

BoltRPC covers both Polygon mainnet and Amoy testnet. One account, one API key, consistent infrastructure from development through production.

Methods

Full JSON-RPC coverage.

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

standard

eth_call eth_sendRawTransaction eth_getBalance eth_blockNumber eth_getTransactionReceipt

FAQ

Polygon, explained.

Common questions about connecting to Polygon over BoltRPC.

Ask a question Read the docs

: The Polygon Amoy Testnet RPC URL with BoltRPC is `https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY`. Replace `YOUR_API_KEY` with your API key from [trial.boltrpc.io](https://trial.boltrpc.io). The chain ID is 80002.
: Polygon Amoy replaced Mumbai as the official Polygon PoS testnet in 2024. Mumbai was deprecated and is no longer supported. If you are still using Mumbai endpoints, migrate to Amoy, it mirrors the current Polygon Mainnet stack.
: Use the official Polygon Amoy faucet at faucet.polygon.technology. You will need a small amount of Sepolia ETH in your wallet to request test tokens. Tokens are free and only valid on the Amoy testnet.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Polygon Amoy, RPC URL: `https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY`, Chain ID: 80002, Currency Symbol: MATIC, Block Explorer: https://amoy.polygonscan.com.
: Public testnet RPCs are shared and often unreliable: they drop connections during congestion, return stale data, and impose strict rate limits. For production development workflows with automated testing and CI/CD pipelines, a reliable testnet endpoint saves significant debugging time. When a CI/CD pipeline fails because the public testnet endpoint is temporarily congested, your team loses time debugging infrastructure rather than shipping product. BoltRPC's testnet access is included in all plans at no additional cost alongside mainnet access.
: Amoy is the current official Polygon PoS testnet, replacing Mumbai in 2024. Mumbai was deprecated because it ran an older version of the Polygon stack that no longer matched mainnet. Amoy mirrors the current Polygon Mainnet configuration, including the POL token upgrade. Any code written for Mumbai should be retested on Amoy before deploying to mainnet.
: Yes. BoltRPC uses one API key across all supported networks. Your Amoy URL is `https://eu.endpoints.matrixed.link/rpc/polygon-amoy?auth=YOUR_API_KEY` and your mainnet URL is `https://eu.endpoints.matrixed.link/rpc/polygon?auth=YOUR_API_KEY`. Same key, same format, just a different network slug. This makes environment management straightforward: store the network slug as an environment variable and switch between testnet and mainnet deployments without touching authentication configuration. Your CI/CD pipeline, staging environment, and production deployment all use the same API key and the same endpoint format.
: Polygon Amoy Testnet uses chain ID 80002. This is different from Polygon Mainnet's chain ID (137). When configuring wallets, libraries, or smart contract deployment scripts for Amoy, verify the chain ID is set to 80002 to avoid broadcasting transactions to the wrong network. The chain ID mismatch is the most common source of "network not found" errors when switching between Polygon mainnet and Amoy in development.

Polygon