Agents on RPCLAW
Give your agent direct access to Base. No API keys, no rate-limit dances, no subscription management. Just JSON-RPC over HTTPS.
Why RPCLAW for agents
🔑 No API key needed
Basic calls work without authentication. Your agent can start querying Base immediately.
💳 Pay-per-call
x402 micropayments in USDC. No monthly bills — the agent pays $0.0000002 per request as it goes.
🗄️ Full history
Archive node serves any block back to genesis. Historical analysis, backtesting, forensics — all available.
📡 WebSocket
Real-time block and event subscriptions via ws.rpclaw.net.
Quick start
Point your agent at the RPC endpoint. That's it.
# Get the latest block
curl -X POST https://rpc.rpclaw.net/v1/base \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
# Check a balance
curl -X POST https://rpc.rpclaw.net/v1/base \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","latest"],"id":1}'
Agent framework examples
ethers.js / viem
// ethers.js
const provider = new ethers.JsonRpcProvider(
"https://rpc.rpclaw.net/v1/base"
);
const block = await provider.getBlockNumber();
// viem
const client = createPublicClient({
transport: http("https://rpc.rpclaw.net/v1/base"),
});
Python (web3.py)
from web3 import Web3
w3 = Web3(Web3.HTTPProvider(
"https://rpc.rpclaw.net/v1/base"
))
print(w3.eth.block_number)
OpenClaw Skill
If your agent runs on OpenClaw, install the RPCLAW operator skill to give it the ability to set up nodes, manage registration, send heartbeats, and monitor health — autonomously.
Install the skill
openclaw skill install https://rpclaw.net/rpclaw-node-operator.skill
Or download directly: rpclaw-node-operator.skill (4 KB)
What the skill teaches your agent
Deploy a Base node
Run curl -sSf https://rpclaw.net/install.sh | bash — the agent knows the full install flow.
Register with the gateway
Idempotent POST /v1/operators/register — safe to call repeatedly.
Send heartbeats
Keep operator status active with automated 5-minute heartbeat calls.
Monitor node health
Bundled healthcheck.sh checks local node, operator status, and gateway.
Troubleshoot issues
Symptom → check → fix table for common problems (sync stuck, heartbeat 404, high disk, etc).
Understand the economics
80/20 fee split, contract addresses, token distribution — all in the skill's reference files.
Skill contents
rpclaw-node-operator/
├── SKILL.md # Core instructions
├── scripts/
│ └── healthcheck.sh # Node + operator + gateway health
└── references/
├── contracts.md # Contract addresses & ABIs
└── systemd-heartbeat.md # Automated heartbeat timer
Health API for agent monitoring
Your agent can programmatically check the network status:
# Node health (fast + archive)
curl https://rpc.rpclaw.net/v1/nodes
# Returns: status, block, syncing, human-readable message
# Operator network stats
curl https://rpc.rpclaw.net/v1/operators/stats
# Returns: totalOperators, activeOperators
# Simple health check
curl https://rpc.rpclaw.net/health