| name | drpc-official-agent-skills |
| description | [](https://github.com/drpcorg/drpc-agent-skills) |
drpc-official-agent-skills
Source: github.com/drpcorg/drpc-agent-skills. The body below is the upstream README.md captured at the time of registration.
DRPC Agent Skills
Give your AI coding agent access to 100+ blockchains over RPC. Works on first ask -- no restart, no config file editing. Agents with a wallet get an API key automatically via x402 -- no signup needed. Guided recipes, error handling, 200+ networks.
Why DRPC? Your requests go through a decentralized gateway that routes across multiple providers. If one is down, another picks up. Responses are consensus-validated, so you don't get bad data from a single node.
What Can You Do?
Type a plain English prompt. The agent figures out which RPC calls to make.
| Use Case | Example Prompt |
|---|
| DeFi Portfolio | "Get my wallet balance across Ethereum, Arbitrum, and Base" |
| Gas Optimization | "Compare gas prices across all L2 networks right now" |
| Transaction Tracking | "Check if transaction 0xabc... is confirmed on Optimism" |
| Smart Contract Reading | "Read the totalSupply of USDC contract on Base" |
| Whale Watching | "Get the last 10 transactions for this address on Ethereum" |
| Cross-Chain Analysis | "Compare TVL-related contract data across Arbitrum, Base and Optimism" |
Install
Works with: Claude Code · Gemini CLI · Cursor · Codex · Windsurf · Cline · OpenClaw
If your agent has a wallet, it gets an API key automatically via x402 -- no signup. Otherwise, get a free key at drpc.org. Then install the skill for your platform:
Claude Code
claude plugins marketplace add drpcorg/drpc-agent-skills
claude plugins install drpc-agent-skills
Gemini CLI
gemini extensions install https://github.com/drpcorg/drpc-agent-skills
Codex
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc ~/.agents/skills/drpc-rpc
Cursor
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .cursor/skills/drpc-rpc
Windsurf
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .windsurf/skills/drpc-rpc
Cline
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .cline/skills/drpc-rpc
OpenClaw
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc ~/.openclaw/skills/drpc-rpc
How It Works
Ask something like:
"Get the ETH balance of vitalik.eth on Ethereum"
"Compare gas prices across all L2 networks"
The agent reads the skill file, picks the right RPC method, calls DRPC, and gives you back the result. No boilerplate on your end.
You ask → Agent reads skill → Calls DRPC API → Returns blockchain data
Three modes, picked automatically:
- First session: acquires API key via x402 wallet signing (or asks you for one), executes request via direct HTTP (no restart needed), configures MCP for future sessions
- Subsequent sessions: uses native MCP tools (faster, integrated)
- Error handling: recognizes billing limits, rate limiting, and guides recovery
x402: Automatic API Key Acquisition
This skill implements the x402 payment protocol -- an open standard by Coinbase for machine-to-machine payments over HTTP. When a server returns 402 Payment Required, the client knows exactly what to pay, signs the payment, and gets access. No accounts, no dashboards, no copy-pasting keys.
Our implementation adds a free shortcut on top of the standard flow:
Agent has wallet?
│
├─ yes → SIWE sign-in (EIP-4361) ─── wallet already linked? ─── yes → API key (free, instant)
│ │
│ no
│ ↓
│ Pay 5 USDC (EIP-3009 signature, settled on Base)
│ ↓
│ API key + tx receipt
│
└─ no → Ask user for key (fallback to drpc.org free tier)
- SIWE check first -- the agent signs a message proving wallet ownership. If that wallet is already tied to a DRPC account, the API key comes back immediately at no cost.
- Payment only when needed -- for new wallets, the agent signs an EIP-3009
transferWithAuthorization for USDC on Base. The server settles it on-chain and returns the key.
- Graceful fallback -- no wallet? The agent asks the user for a key the old-fashioned way.
All signatures are off-chain (no gas for the user). Settlement happens server-side.
See x402-auto-key.md for the full protocol recipe with curl examples.
Skill Contents
MCP Tools
| Tool | Description |
|---|
list_networks | All 200+ supported networks |
list_methods | RPC methods for a network |
get_network_info | Network details (chain ID, currency, explorers) |
eth_getBalance | Native token balance |
eth_getBlockByNumber | Block by number or tag |
eth_getBlockByHash | Block by hash |
eth_getTransactionByHash | Transaction details |
eth_getTransactionReceipt | Receipt with status and logs |
eth_getLogs | Event log queries |
eth_call | Read smart contracts |
eth_gasPrice | Current gas price |
eth_estimateGas | Gas estimation |
eth_getCode | Contract bytecode |
eth_getTransactionCount | Nonce for address |
rpc_call | Any JSON-RPC method |
rpc_batch | Batch multiple calls |
Supported Networks
Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, zkSync, Linea, Scroll, Mantle, Fantom, Gnosis, Celo, Moonbeam, Harmony, Aurora, Metis, Boba, Cronos, Klaytn, Solana, Bitcoin, NEAR, Cosmos, Starknet, and many more.
Contributing
Found a bug? Missing a chain? Open an issue or send a PR.
Stars help with discoverability -- if this saved you time, consider leaving one.
License
MIT
