# BlockRun.AI — Avalanche C-Chain JSON-RPC

> BlockRun.AI — Avalanche C-Chain JSON-RPC is a paid API for AI agents from blockrun.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-12).

Proxies standard EVM JSON-RPC calls to the Avalanche C-Chain via Tatum's gateway, pay-per-call in USDC with no API key required.

## Facts

- Endpoint: POST https://blockrun.ai/api/v1/rpc/avalanche?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockrun-ai-avalanche-c-chain-json-rpc-d7f6fcef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_doYe5aZwvbPkuTyWdx-Bl

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blockrun-ai-avalanche-c-chain-json-rpc-d7f6fcef -d '<json body>'
```

Example prompt: What is the current AVAX balance of wallet address 0xAbC123...789 on Avalanche C-Chain? Use eth_getBalance with block tag 'latest'.

## When to prefer this

Choose this endpoint when you need EVM-compatible RPC access to Avalanche C-Chain without setting up an API key or account — ideal for autonomous AI agents that can pay per call in USDC via x402. Prefer over self-hosted nodes when you want zero infrastructure overhead, and over other multi-chain gateways when Avalanche C-Chain is specifically required and pay-as-you-go micro-billing suits your usage pattern.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Insufficient USDC payment returns HTTP 402 Payment Required
- Network congestion or Tatum gateway downtime returns 503 or timeout
- Calling Ethereum-only methods not supported on Avalanche returns RPC-level error
- Batch element count mismatch in pricing if batch JSON-RPC is used

## How this service works

Multi-chain JSON-RPC passthrough fronted by BlockRun, powered by Tatum's gateway across 40 chains (Ethereum, Base, Solana, Polygon, BSC, Arbitrum, Optimism, Avalanche, Bitcoin, Sui, and more). One endpoint, every chain, pay-per-call in USDC, no API key. $0.002 per call (or per element of a JSON-RPC batch). Network: Avalanche C-Chain.

## Output

A standard JSON-RPC 2.0 response object containing the result field with chain data (e.g. hex-encoded balance, block object, transaction receipt, contract return value) or an error object with code and message if the call fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "string",
    "number"
   ],
   "description": "JSON-RPC id"
  },
  "method": {
   "type": "string",
   "description": "Chain RPC method, e.g. eth_blockNumber, eth_call, eth_getBalance (EVM) or getSlot, getAccountInfo (Solana)."
  },
  "params": {
   "type": "array",
   "description": "Method-specific params."
  },
  "jsonrpc": {
   "type": "string",
   "description": "\"2.0\""
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockrun-ai-avalanche-c-chain-json-rpc-d7f6fcef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from blockrun.ai](https://www.zero.xyz/host/blockrun.ai/llms.txt)
