agentleFS
BlockRunAIBlockRunAI/blockrun-mcp/skills/rpc/SKILL.md

rpc

Skill389 starsChanged 23 days agoMITView on GitHub

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, no API key. Prefer blockrun_price / blockrun_dex / the paid tools when they already cover the question.

The file

Files
SKILL.md

Multi-chain RPC — every supported chain, one tool

blockrun_rpc POSTs a standard JSON-RPC 2.0 body to /v1/rpc/{network}. Flat $0.0030 per call ($0.002 base + the $0.001 transaction fee). A JSON-RPC batch array charges per element but pays the flat fee only once — $0.002 × n + $0.001, so a batch of 3 costs $0.0070 where three separate calls cost $0.0090. Batch whenever you can. Settlement in USDC via x402. Responses are cached briefly server-side for identical read calls (X-Cache: HIT is free of upstream latency but still billed).

When to use which tool

QuestionTool
"What's ETH trading at?"blockrun_price (free)
"PEPE/WETH pool liquidity?"blockrun_dex (free)
"What's this wallet holding?"blockrun_rpc (labels: no tool since Surf was retired 2026-09-06)
"Call balanceOf(0x...) on this ERC-20"blockrun_rpc
"Latest block / tx receipt / event logs / gas price"blockrun_rpc
"Solana account info / slot / signatures"blockrun_rpc

Networks

EVM (use eth_* methods):

KeyChainKeyChain
ethereumEthereumzksynczkSync Era
baseBaseberachainBerachain
arbitrumArbitrum OneunichainUnichain
arbitrum-novaArbitrum NovamonadMonad
optimismOptimismchilizChiliz
polygonPolygonmoonbeamMoonbeam
bscBNB Smart ChainauroraAurora
avalancheAvalanche C-ChainflareFlare
fantomFantomoasisOasis Sapphire
cronosCronoskaiaKaia (Klaytn)
celoCelosonicSonic
gnosisGnosisxdcXDC Network
abstractAbstracthyperevmHyperEVM
plumePlumeroninRonin
rootstockRootstock (RSK)

Non-EVM (chain-native methods):

KeyChainMethod family
solanaSolanagetSlot, getBalance, getAccountInfo, getSignaturesForAddress
bitcoinBitcoingetblockchaininfo, getblockcount, getrawtransaction
litecoin / dogecoin / bitcoin-cash / zcashUTXO chainsBitcoin-style RPC
nearNEARstatus, query
suiSuisui_getLatestCheckpointSequenceNumber, suix_getBalance
rippleXRP Ledgeraccount_info, ledger
polkadot / kusamaSubstratechain_getHeader, state_getStorage

Unknown-but-wellformed slugs pass through to the Tatum gateway untouched — newly added chains work without an MCP update. A bad slug returns HTTP 400 with the supported list (no charge).

Recipes

ERC-20 balance (eth_call):

blockrun_rpc({
  network: "base",
  method: "eth_call",
  params: [{
    to: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",   // USDC on Base
    data: "0x70a08231000000000000000000000000<ADDRESS_NO_0x_PADDED_TO_32B>"
  }, "latest"]
})

Native balance: method: "eth_getBalance", params: ["0x...", "latest"] Tx receipt: method: "eth_getTransactionReceipt", params: ["0x<txhash>"] Event logs: method: "eth_getLogs", params: [{ fromBlock, toBlock, address, topics }] — keep ranges small; huge ranges are rejected upstream (no charge). Gas: method: "eth_gasPrice" / eth_estimateGas

Solana token account: network: "solana", method: "getTokenAccountsByOwner", params: ["<owner>", {"mint": "<mint>"}, {"encoding": "jsonParsed"}]

Batch (charged per element, flat fee paid once — 3 calls = $0.0070, vs $0.0090 sent separately):

blockrun_rpc({ network: "ethereum", body: [
  { jsonrpc: "2.0", id: 1, method: "eth_blockNumber" },
  { jsonrpc: "2.0", id: 2, method: "eth_gasPrice" },
  { jsonrpc: "2.0", id: 3, method: "eth_chainId" }
]})

Failure semantics

  • Upstream timeout / 5xx → no charge, retry safe.
  • Malformed body / bad network → HTTP 400, no charge.
  • JSON-RPC-level errors (e.g. revert on eth_call) come back inside result.error — the call is charged (the node did the work).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.