drpc-rpc
/drpc-rpc
Use when the user needs blockchain data (balances, transactions, blocks, gas prices, contract reads), wants to set up blockchain RPC access, or mentions DRPC, Web3, or Ethereum RPC. Also triggers on specific method names like eth_getBalance, eth_call, eth_getLogs.
- Author
- drpcorg ↗
- Repository
- drpc-agent-skills ↗
- Licence
- MIT
- Last repository change
- 21.06.2026
Assessment and security
- Files in this package
- 11
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 21.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user needs blockchain data (balances, transactions, blocks, gas prices, contract reads), wants to set up blockchain RPC access, or mentions DRPC, Web3, or Ethereum RPC. Also triggers on specific method names like eth_getBalance, eth_call, eth_getLogs.
Original author description
Use when the user needs blockchain data (balances, transactions, blocks, gas prices, contract reads), wants to set up blockchain RPC access, or mentions DRPC, Web3, or Ethereum RPC. Also triggers on specific method names like eth_getBalance, eth_call, eth_getLogs.
How it works
- Step 1: Detect Transport
- Step 2: Auto-Acquire API Key via x402
- Step 3: Fallback — Ask User for API Key
- Step 4: Configure MCP + Execute Current Request
- Step 5: Route by Query Type
- Error Handling
- Quick Reference
SKILL.md preview
--- name: drpc-rpc description: Use when the user needs blockchain data (balances, transactions, blocks, gas prices, contract reads), wants to set up blockchain RPC access, or mentions DRPC, Web3, or Ethereum RPC. Also triggers on specific method names like eth_getBalance, eth_call, eth_getLogs. --- # DRPC RPC — Blockchain Access for AI Agents 100+ blockchains, 200+ networks via DRPC decentralized RPC gateway. ## Step 1: Detect Transport Check if DRPC MCP tools are available (look for `list_networks`, `eth_getBalance`, `rpc_call`). - **MCP tools found** → use them directly. Go to Step 5. - **MCP tools NOT found** → go to Step 2. ## Step 2: Auto-Acquire API Key via x402 If you have access to an EVM wallet (private key or signer), try to get an API key automatically using the x402 protocol. See [x402-auto-key.md](x402-auto-key.md) for the full flow. Summary: 1. Sign in with wallet (SIWE) — if wallet is known, get key for free. 2. If wallet is new, pay with USDC (EIP-3009) — get key after on-chain settlement. - **Got `api_key`** → go to Step 4. - **No wallet or any failure** → go to Step 3. ## Step 3: Fallback — Ask User for API Key Ask user for their DRPC API key. If they don't have one, direct them to https://drpc.org (free tier available). ## Step 4: Configure MCP + Execute Current Request Once you have an API key (from Step 2 or Step 3): 1. **Execute the current request now** using direct HTTP calls — no restart needed. See [direct-http.md](direct-http.md) for the curl format. 2. **Configure MCP for future sessions.** See [setup.md](setup.md) for platform-specific commands. 3. **Tell the user:** "Done. Next session will use native MCP tools (faster)." ## Step 5: Route by Query Type | User wants... | Reference | |---------------|-----------| | Tool parameters, return formats | [tools-reference.md](tools-reference.md) | | Single-network query (balance, tx, block, gas, contract) | [recipes-simple.md](recipes-simple.md) | | Multi-network comparison, cross-chain tracking | [recipes-crosschain.md](recipes-crosschain.md) | | DeFi: portfolio, approvals, LP tokens, staking | [recipes-defi-basics.md](recipes-defi-basics.md) | | DeFi: Aave, Uniswap, Lido, Morpho, Curve | [recipes-defi-protocols.md](recipes-defi-protocols.md) | | x402 auto-key flow | [x402-auto-key.md](x402-auto-key.md) | | Client-specific routing/repro (`reth`, `geth`, `erigon`, etc.) | [client-selection.md](client-selection.md) | | Error handling, billing issue | [errors.md](errors.md) | | Setup or reconfigure MCP | [setup.md](setup.md) | ## Error Handling If any call returns an error, check [errors.md](errors.md) before retrying. Key signals: - **HTTP 403** → billing/auth error (codes 10, 24, 52, 53, 4, 9) - **HTTP 429** → rate limited (code 31) — retry after 1-2s - **HTTP 408** → timeout (codes 40, 46) - **HTTP 400** → bad request or feature restriction (codes 11, 47, 51) ## Quick Reference - Addresses: 0x-prefixed, 42-char hex - Block tags: `"latest"`, `"earliest"`, `"safe"`, `"finalized"`, or hex number - Values: hex strings in wei. ETH = wei / 10^18, gwei = wei / 10^9 - Use `list_networks` first if unsure about network names - MCP tools usually do not expose routing hints; use [client-selection.md](client-selection.md) for direct JSON-RPC calls with `clients=reth`, `client_type=geth`, etc. - Use `rpc_batch` for multiple queries on the same network - Use `rpc_call` for non-EVM chains (Solana, Bitcoin, NEAR, Cosmos)
Files in this package (11)
- SKILL.md 3 KB
- client-selection.md 4 KB
- direct-http.md 3 KB
- errors.md 3 KB
- recipes-crosschain.md 3 KB
- recipes-defi-basics.md 5 KB
- recipes-defi-protocols.md 7 KB
- recipes-simple.md 2 KB
- setup.md 2 KB
- tools-reference.md 3 KB
- x402-auto-key.md 6 KB
Versions
The database has no other skills named drpc-rpc.
Database snapshot: 13.11.2026 · package version 8bc4ed433407 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90drpc-rpc-pi
Pi Agent-specific DRPC setup flow. Use alongside drpc-rpc when the user asks for blockchain data, DRPC setup, x402 API-key acquisition, Coinbase Payments MCP, pi-mcp-adapter, or when DRPC MCP is not configured in Pi. - 100rpc
Use when the user needs raw blockchain JSON-RPC access — contract reads (eth_call), native balances, blocks, transactions, logs, gas estimates, or any chain-native RPC method across 40 chains. One endpoint per chain via BlockRun's Tatum-backed gateway, $0.0030 per call, no node,… - 100exploring-blockchain-data
Process query and analyze blockchain data including blocks, transactions, and smart contracts. Use when querying blockchain data and transactions. Trigger with phrases like "explore blockchain", "query transactions", or "check on-chain data". - 100exploring-blockchain-data
Process query and analyze blockchain data including blocks, transactions, and smart contracts. Use when querying blockchain data and transactions. Trigger with phrases like "explore blockchain", "query transactions", or "check on-chain data". - 100alchemy
Blockchain API access via Alchemy. Use when an agent needs to query blockchain data (balances, token prices, NFT ownership, transfer history, transaction simulation, gas estimates) across Ethereum, Base, Arbitrum, BNB, Polygon, Solana, and more. Supports API key access… - 100data
Querying Stellar chain data via Stellar RPC (preferred) and Horizon (legacy). Covers RPC JSON-RPC methods, Horizon REST endpoints, streaming, pagination, historical queries, Hubble/Galexie for deep history, and the RPC/Horizon migration story. Use when reading balances,…