# Pocket Network – Fuse Mainnet JSON-RPC

> Pocket Network – Fuse Mainnet JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-03).

Provides read-only Ethereum-compatible JSON-RPC access to the Fuse network mainnet via Pocket Network's decentralised relay infrastructure, billed per request in USDC.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/fuse?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-fuse-mainnet-json-rpc-0a40be13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e_8KqpKRbcnOcIJ3Zg1Yl

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 pocket-network-fuse-mainnet-json-rpc-0a40be13 -d '<json body>'
```

Example prompt: What's the current FUSE balance of wallet 0xAbC...123 on Fuse mainnet? Use eth_getBalance with block tag 'latest'.

## When to prefer this

Choose this endpoint when you need reliable, decentralised, read-only RPC access to the Fuse EVM-compatible L1 blockchain without managing API keys or accounts. It is ideal for agents that need pay-per-use pricing in USDC with no subscription commitment, and whose Fuse-specific queries are infrequent or unpredictable in volume. Prefer it over centralised RPC providers when censorship-resistance and supplier decentralisation matter.

## Known failure modes

- Invalid or unsupported method name returns JSON-RPC error -32601
- Malformed params return error -32602 (invalid params)
- Payment not fulfilled causes 402 Payment Required before relay
- Rate limits or supplier unavailability may return 503 or timeout
- Write methods (eth_sendRawTransaction) are not supported — returns error
- Querying a block or transaction that doesn't exist returns null result

## How this service works

Read-only JSON-RPC access to Fuse mainnet, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

## Output

A standard Ethereum JSON-RPC response object containing a 'result' field with the requested on-chain data (balance in wei, block object, transaction receipt, log array, gas estimate, etc.) or an 'error' field with code and message if the request failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "debug_getBadBlocks",
    "debug_getRawBlock",
    "debug_getRawHeader",
    "debug_getRawReceipts",
    "debug_getRawTransaction",
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_config",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "eth_getTransactionByBlockHashAndIndex",
    "eth_getTransactionByBlockNumberAndIndex",
    "eth_getTransactionByHash",
    "eth_getTransactionCount",
    "eth_getTransactionReceipt",
    "eth_getUncleByBlockHashAndIndex",
    "eth_getUncleByBlockNumberAndIndex",
    "eth_getUncleCountByBlockHash",
    "eth_getUncleCountByBlockNumber",
    "eth_maxPriorityFeePerGas",
    "eth_newBlockFilter",
    "eth_newFilter",
    "eth_newPendingTransactionFilter",
    "eth_simulateV1",
    "eth_syncing",
    "eth_uninstallFilter",
    "net_listening",
    "net_peerCount",
    "net_version",
    "txpool_status",
    "web3_clientVersion",
    "web3_sha3"
   ],
   "description": "JSON-RPC read method, e.g. eth_getBalance"
  },
  "params": {
   "description": "Parameters per the Ethereum JSON-RPC spec"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": 1,
   "result": false,
   "jsonrpc": "2.0"
  },
  "portal": {
   "serviceId": "fuse",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-fuse-mainnet-json-rpc-0a40be13/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)