drpc-rpc

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 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 for the curl format.
2. Configure MCP for future sessions. See 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
Single-network query (balance, tx, block, gas, contract)	recipes-simple.md
Multi-network comparison, cross-chain tracking	recipes-crosschain.md
DeFi: portfolio, approvals, LP tokens, staking	recipes-defi-basics.md
DeFi: Aave, Uniswap, Lido, Morpho, Curve	recipes-defi-protocols.md
x402 auto-key flow	x402-auto-key.md
Error handling, billing issue	errors.md
Setup or reconfigure MCP	setup.md

Error Handling

If any call returns an error, check 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
• Use rpc_batch for multiple queries on the same network
• Use rpc_call for non-EVM chains (Solana, Bitcoin, NEAR, Cosmos)