DRPC RPC — Blockchain Access Skill for AI Agents
Lets AI coding agents query 100+ blockchains across 200+ networks via the DRPC decentralized gateway on the very first ask — wallet-equipped agents get an API key automatically through x402, no signup required.
Data flow is transparently disclosed: API key acquisition, x402 wallet signing and on-chain USDC payment are all documented with a manual fallback (user-supplied key). No hard-coded secrets; repeated warnings not to leak keys. Deductions: Step 2 lets the agent automatically sign with the user's EVM wallet and pay 5 USDC without an explicit user-confirmation gate; API keys sit in URL paths and may leak into logs; publisher unverified, update/revocation path unclear. Not a red line, but authorization/confirmation is incomplete.
Files are internally consistent: transport detection, direct HTTP, the error-code table and recovery patterns interlock; failure feedback is detailed (HTTP codes, DRPC codes, actions) and explains why it cannot proceed. Deductions: static review only — endpoint behavior, SSE format and the x402 flow are unverified; no test suite or committed reproduction evidence; the x402 auto-key critical path especially depends on unverified external services.
Trigger conditions are specific (eth_getBalance, DRPC, Web3, etc.), scenarios are clear (balances, transactions, cross-chain, DeFi), and capability boundaries are stated (client selection is a routing hint, not machine pinning). Deductions: core function depends entirely on overseas services (lb.drpc.org, drpc.org, USDC on Base) with no mainland-China reachability statement; no Chinese support; non-fit ranges only partially declared.
Good layered information architecture (entry point → routing by query type to topic files), install instructions across 8 platforms, clear MIT license, maintenance by the drpcorg org. Deductions: version is only 0.1.0 with no changelog; tools-reference.md and x402-auto-key.md were not provided in this review so referenced completeness cannot be confirmed; known-limitation disclosure is scattered.
Recipes (balance, gas comparison, Aave/Uniswap positions, etc.) come with concrete curls and selectors and claim directly presentable tabular output; marginal value is clear (avoids hand-writing RPC boilerplate). Deductions: under static review direct usability is unconfirmed; example outputs are illustrative, not verified results; some sample data (gas table) is clearly fabricated snapshots.
Substantial auditable primary material is present: complete curl commands, function selectors, real contract addresses, error-code tables enabling independent reproduction. Deductions: no execution evidence, no CI workflows or committed tests covering key paths; claims like '200+ networks' link only to an external site unverifiable in-repo; example outputs are uncorroborated.
- The x402 flow signs with an EVM wallet the agent can access and may pay 5 USDC (EIP-3009, settled on Base); confirm wallet permission scope before use and consider disabling the auto-payment step.
- API keys are passed in URL paths and may appear in shell history, proxies, or server logs; read keys from environment variables and avoid logging full URLs as the docs suggest.
- This review is static source reading only; no calls were executed. Endpoint formats, SSE responses and error codes are unverified by testing.
- Core function depends entirely on overseas services (lb.drpc.org, drpc.org) and USDC payment on Base; mainland-China network reachability is undeclared and may be unstable.
- Example outputs (balances, gas prices, DeFi positions) are illustrative fabricated data; verify real results independently.
- Publisher is not verified by the FollowSkills curated registry; identity is treated as unknown.
What does this skill do, and when should you use it?
drpc-rpc is an Agent Skill that gives AI coding agents direct blockchain RPC access across 100+ chains and 200+ networks, including Ethereum, Arbitrum, Base, Solana, and Bitcoin. On startup it detects whether DRPC MCP tools are available; if not, it acquires an API key automatically via the x402 protocol (free SIWE sign-in for linked wallets, 5 USDC via EIP-3009 for new ones) or falls back to asking the user. The first request executes immediately over direct HTTP — no restart or config editing — while MCP is configured for faster native tools in future sessions. Routing recipes cover single-chain queries, cross-chain comparison, DeFi protocols, client-specific routing, and structured error handling by HTTP status code.
Detects whether DRPC MCP tools (list_networks, eth_getBalance, rpc_call) are present in the session. If absent, runs the x402 flow: SIWE wallet signature (EIP-4361) for a free key if the wallet is already linked, or an EIP-3009 transferWithAuthorization for 5 USDC on Base for new wallets; without a wallet it asks the user for a DRPC key or points them to the drpc.org free tier. Once a key exists, it executes the current request via direct curl JSON-RPC calls (balances, blocks, transactions, gas, contract reads, event logs) and configures MCP for later sessions. Queries are routed by type to reference files: tools parameters/return formats, single-network recipes, cross-chain recipes, DeFi basics (portfolio, approvals, LP tokens, staking), DeFi protocols (Aave, Uniswap, Lido, Morpho, Curve), client selection (reth/geth/erigon), errors, and setup. Errors are classified by HTTP status: 403 billing/auth, 429 rate limited (retry after 1–2s), 408 timeout, 400 bad request. Non-EVM chains (Solana, Bitcoin, NEAR, Cosmos) use rpc_call; multiple queries on one network use rpc_batch.
- A DeFi user wants their agent to fetch wallet balances across Ethereum, Arbitrum, and Base in one prompt
- A developer needs to read contract data (e.g. totalSupply of USDC on Base) or a transaction receipt without hand-writing RPC boilerplate
- A cross-chain analyst wants the agent to compare TVL-related contract data across Arbitrum, Base, and Optimism, or real-time gas prices across L2s
- A whale-watcher wants the last 10 transactions for a given address on Ethereum
- A user with a DRPC key but no MCP setup wants their first-session request executed immediately, with no restart and no manual config-file edits
What are this skill's strengths and limitations?
- Works on the first ask — no agent restart and no manual config-file editing
- Wallet-equipped agents get a key automatically via x402; SIWE-linked wallets get it free, and all signatures are off-chain so users pay no gas
- DRPC's decentralized gateway routes across multiple providers with consensus validation, so a single bad node doesn't corrupt responses
- Covers 100+ chains and 200+ networks, including non-EVM chains (Solana, Bitcoin, NEAR, Cosmos)
- Ships with query-type recipes and structured error-code handling (billing, rate limits, timeouts), plus client-level routing (reth, geth, erigon)
- New wallets must pay 5 USDC (settled on Base) for a key; free acquisition applies only to already-linked wallets
- Depends on the third-party DRPC gateway — availability and pricing are bound to DRPC's terms
- No public test suite or independent performance benchmarks; platform claims like OpenClaw and Pi Agent are not verified in the source material
- MCP tools usually do not expose routing hints, so client selection requires falling back to direct JSON-RPC calls — added complexity
- Rate-limit (429) recovery is a manual retry after a suggested wait; there is no automatic retry mechanism
How do you install this skill?
The skill collection supports eight platforms: Claude Code, Gemini CLI, Codex, Pi Agent, Cursor, Windsurf, Cline, OpenClaw. Claude Code: claude plugins marketplace add drpcorg/drpc-agent-skills, then claude plugins install drpc-agent-skills. Cursor: git clone https://github.com/drpcorg/drpc-agent-skills.git, then ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .cursor/skills/drpc-rpc. Codex, Windsurf, Cline, and OpenClaw likewise use git clone plus a symlink (target directories per README); Gemini CLI uses gemini extensions install; Pi Agent uses pi install. This profile covers only the skills/drpc-rpc skill — the repo bundles a second sibling skill, and the install commands install the whole collection. Per-platform MCP configuration details live in the skill's setup.md; no single universal command is documented in the source.
How do you use this skill?
After installation, ask in plain English, e.g. "Get the ETH balance of vitalik.eth on Ethereum", "Compare gas prices across all L2 networks", or "Check if transaction 0xabc... is confirmed on Optimism". The agent reads SKILL.md and detects available MCP tools; without tools and with an EVM wallet, it first obtains a key via x402 (free SIWE or 5 USDC), executes the current request with curl, and tells you the next session will use faster native MCP tools. Call list_networks first if unsure about network names. Values are hex wei (ETH = wei / 10^18, gwei = wei / 10^9); on errors consult errors.md, classified by status code (403 billing, 429 rate-limit with retry, 408 timeout, 400 bad request).