RPC for AI Agents

Most AI agents and MCP servers read the blockchain through a JSON-RPC endpoint — and most default to a rate-limited public endpoint that isn't meant for production (Base's own docs say exactly this about mainnet.base.org). Swap in NodeFlare and your agent runs on our own bare-metal nodes across 5 regions, on 23 EVM chains, with automatic failover — no account required, a free key for higher limits, or pay-per-call over x402.

The endpoint#

https://rpc.nodeflare.app/{chain}/public          # no key
https://rpc.nodeflare.app/{chain}/v1/{YOUR_KEY}    # free key: higher limits, eth_getLogs, WebSocket
https://rpc.nodeflare.app/{chain}/x402             # pay-per-call in USDC, no account

{chain} is a slug like base, eth, arb, robinhood, plasma — see all 23 chains. A free key unlocks 2,000,000 compute units/month, WebSocket, and heavy methods (eth_getLogs, trace_*, debug_*).

Libraries every agent uses under the hood#

viem#

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

const client = createPublicClient({
  chain: base,
  transport: http("https://rpc.nodeflare.app/base/v1/YOUR_KEY"),
});

ethers.js#

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://rpc.nodeflare.app/base/v1/YOUR_KEY");

wagmi#

import { createConfig, http } from "wagmi";
import { base, mainnet } from "wagmi/chains";

export const config = createConfig({
  chains: [base, mainnet],
  transports: {
    [base.id]:    http("https://rpc.nodeflare.app/base/v1/YOUR_KEY"),
    [mainnet.id]: http("https://rpc.nodeflare.app/eth/v1/YOUR_KEY"),
  },
});

web3.py (Python agents)#

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.nodeflare.app/base/v1/YOUR_KEY"))

MCP servers#

NodeFlare MCP (the simplest option)#

Our own MCP server exposes JSON-RPC on all 23 chains as agent tools — no wiring needed:

{
  "mcpServers": {
    "nodeflare": { "command": "npx", "args": ["-y", "nodeflare-mcp"] }
  }
}

Set NODEFLARE_API_KEY for higher limits, or X402_PRIVATE_KEY to pay heavy calls per request. See /agents.

evm-mcp-server and other RPC-configurable MCP servers#

MCP servers that read EVM chains take an RPC URL (env var or per-network config). Point it at NodeFlare:

# generic pattern — set the RPC URL the server uses
EVM_RPC_URL="https://rpc.nodeflare.app/base/v1/YOUR_KEY"

Servers that build their chain list from chainlist.org pick up NodeFlare automatically — we're a listed provider — but pinning our URL gives you production reliability instead of the public default.

Agent frameworks#

Coinbase AgentKit / OnchainKit#

AgentKit uses viem under the hood. Pass a NodeFlare transport to the wallet/client config:

import { http } from "viem";
const transport = http("https://rpc.nodeflare.app/base/v1/YOUR_KEY");
// supply this transport to your AgentKit WalletProvider / viem client

GOAT#

GOAT wraps a viem or ethers client. Build the client with a NodeFlare RPC URL (see the viem/ethers snippets above) and hand it to GOAT's getOnChainTools.

Why NodeFlare for agents#

• Production, not a demo endpoint. Own bare-metal nodes, 5 regions, health-checked automatic failover — unlike the rate-limited public defaults agents ship with.
• 23 chains, one provider. Including young chains (Robinhood Chain, Plasma, Ink, Zircuit) most providers don't serve — where agents otherwise have no reliable RPC.
• Heavy methods included. eth_getLogs, trace_*, debug_* on a free key — the calls indexing and simulation agents actually need.
• Keyless option for autonomous agents. Pay per call in USDC over x402, or discover us in the x402 Bazaar and the official MCP Registry.

Building an agent that needs chain data? Get a free key — 2,000,000 compute units/month, no credit card — or read the agent overview.