OpenParable
Skip to content
← Back to skills

Rpc

Apps & Automation
rpc

Rpc is an Agent Skill for apps & automation published in the BlockRunAI/blockrun-mcp repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.002 per call, no node, no API key. Prefer blockrun_price / blockrun_dex / blockrun_surf when they already cover the question.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/BlockRunAI/blockrun-mcp/blob/HEAD/skills/rpc/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rpc, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Multi-chain RPC — 40+ chains, one tool

blockrun_rpc POSTs a standard JSON-RPC 2.0 body to /v1/rpc/{network}. Flat $0.002 per call; a JSON-RPC batch array charges per element. 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 labeled as / holding?"blockrun_surf
"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 — 3 calls = $0.006):

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).