Skip to content

Multi-chain RPC gateway · by Chord

One URL
per chain.

Open moltnode.ag/monad in a browser and it's a page. POST to the same address and it's JSON-RPC. Built so a person and an agent can share one endpoint.

31 chains · auto-failover · open CORS · no key

probing
$moltnode.ag/monad
requestPOST · eth_blockNumber
response
// awaiting head…

the dual endpoint

The same address behaves two ways

MoltNode reads the request, not just the path. The method decides what comes back.

GET/monad in a browser

A page for humans

Live block height and latency, the providers behind it, one-click add-to-wallet, and copy-paste snippets for viem, ethers and web3.py.

moltnode.ag/monad
operational · block 82,549,437 · 41 ms
POST/monad from code

JSON-RPC for agents

A standard JSON-RPC 2.0 response, single or batched. Failover and key handling happen upstream, so the agent just gets a fast, clean answer.

→ {"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}
← {"jsonrpc":"2.0","id":1,"result":"0x4ea96bd"}

From the makers of MoltNode

Chord: swaps and market data for agents

MoltNode reads the chain. Chord finds the best route and builds the unsigned swap transaction on Monad, Robinhood Chain, Arc, Avalanche, Base and BNB Chain, with market data on Solana too. One MCP URL, no key to start.

Start with Chord

the catalog

31 chains, one pattern

Click any chain for its page, or copy the endpoint and go. Pills probe the live head as you scroll.

Monad

chainId 143·MON

moltnode.ag/monad
·

Ethereum

chainId 1·ETH

moltnode.ag/ethereum
·

Base

chainId 8453·ETH

moltnode.ag/base
·

Arbitrum One

chainId 42161·ETH

moltnode.ag/arbitrum
·

Optimism

chainId 10·ETH

moltnode.ag/optimism
·

Polygon

chainId 137·POL

moltnode.ag/polygon
·

BNB Chain

chainId 56·BNB

moltnode.ag/bnb
·

Solana

SVM·SOL

moltnode.ag/solana
·

Avalanche C-Chain

chainId 43114·AVAX

moltnode.ag/avalanche
·

HyperEVM

chainId 999·HYPE

moltnode.ag/hyperevm
·

Berachain

chainId 80094·BERA

moltnode.ag/berachain
·

Abstract

chainId 2741·ETH

moltnode.ag/abstract
·

Sei

chainId 1329·SEI

moltnode.ag/sei
·

Sonic

chainId 146·S

moltnode.ag/sonic
·

Mantle

chainId 5000·MNT

moltnode.ag/mantle
·

Taiko

chainId 167000·ETH

moltnode.ag/taiko
·

zkSync Era

chainId 324·ETH

moltnode.ag/zksync
·

ZetaChain

chainId 7000·ZETA

moltnode.ag/zetachain
·

opBNB

chainId 204·BNB

moltnode.ag/opbnb
·

BOB

chainId 60808·ETH

moltnode.ag/bob
·

Edge

chainId 3343·ETH

moltnode.ag/edge
·

Stable

chainId 988·USD

moltnode.ag/stable
·

Katana

chainId 747474·ETH

moltnode.ag/katana
·

Morph

chainId 2818·ETH

moltnode.ag/morph
·

Swellchain

chainId 1923·ETH

moltnode.ag/swell
·

0G

chainId 16661·0G

moltnode.ag/0g
·

TAC

chainId 239·TAC

moltnode.ag/tac
·

X Layer

chainId 196·OKB

moltnode.ag/xlayer
·

Gnosis

chainId 100·xDAI

moltnode.ag/gnosis
·

Fantom

chainId 250·FTM

moltnode.ag/fantom
·

Sui

MOVE·SUI

moltnode.ag/sui
·

Automatic failover

Every chain lists multiple providers. A timeout or 5xx silently rolls to the next one.

Keys never leak

Upstream provider keys stay server-side. Callers only ever see the clean URL.

No key, no signup

Open endpoints with open CORS. Paste a URL and you are already calling the chain.

Batch & full methods

Plain JSON-RPC 2.0. Single calls, batch arrays, traces, sends. Nothing stripped.

EVM and beyond

Same clean URL for EVM chains, Solana, and Sui. Each speaks its own JSON-RPC.

Agent-native

One MCP server at /mcp reads every chain and trades through Chord, plus a JSON catalog and an llms.txt.

quickstart

Drop in the URL. That's the integration.

No SDK, no key, no init step. Point your existing client at moltnode.ag/<chain> and keep writing the code you already know.

# any chain, just change the path
curl -X POST https://moltnode.ag/ethereum \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

guides

Start with a guide

All guides

FAQ

Questions, answered

What is MoltNode?

MoltNode is a multi-chain RPC gateway. Every chain has one clean URL. Open it in a browser for a page, or POST JSON-RPC to the same address from code, a wallet, or an AI agent.

What is an RPC endpoint?

An RPC endpoint is the URL your app, wallet, or agent talks to in order to read on-chain data and send transactions. MoltNode gives you one per chain at moltnode.ag/<chain>.

Do I need an API key?

No. Every endpoint is open and CORS is enabled. Paste the URL and start calling, no signup and no key. Upstream provider keys are handled server-side and never exposed.

Is there a rate limit?

Yes. The service is free and shared, so each client gets short bursts of 60 requests, 3 requests per second after that and 20,000 requests per day, and answers larger than 8 MB are not relayed. When a limit is hit the gateway answers 429 or 503 with a Retry-After header. For heavy production traffic, run your own node or a dedicated provider. With a free Chord API key (get one at getchord.xyz/developer, send it as the X-Chord-Key header) every limit is five times higher.

How does automatic failover work?

Each chain lists several upstream providers. If one times out or returns a 429 or 5xx, MoltNode retries the next provider automatically, so your request still gets answered.

Which chains are supported?

31 chains today, including EVM chains, Solana, and Sui. Browse the full catalog on the homepage, or fetch it as JSON at /api/chains.

Can wallets and AI agents use it?

Yes. Add any EVM endpoint to a wallet as a custom network, or point viem, ethers, or web3.py at it. Agents can add the hosted MCP server at moltnode.ag/mcp (no key), or discover every endpoint via /api/chains and /llms.txt.

Can my agent swap tokens?

Yes, through Chord, from the same team. Chord finds the best route across the DEXs of Ethereum, Base, Monad, BNB Chain, Avalanche, Arbitrum, Robinhood Chain and Arc and returns an unsigned transaction with a simulation from your wallet. Your agent signs it with its own key and broadcasts it through MoltNode; nothing is held for you. The MCP server at moltnode.ag/mcp has the tools, and moltnode.ag/trade has a live quote and full code.

Does it support batch requests?

Yes. Send a JSON array of calls in one POST and you get an array of results back, exactly per the JSON-RPC 2.0 spec.