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
Multi-chain RPC gateway
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/monadrequestPOST · 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.
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"}
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.
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
A JSON catalog and an llms.txt so tools can discover every endpoint on their own.
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 pathcurl -X POST https://moltnode.ag/ethereum \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'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?
There is no hard public limit today, but the service is shared, so please use it responsibly. For heavy production traffic, run your own node or a dedicated provider.
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 discover every endpoint via /api/chains and /llms.txt.
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.