# QuickNode JSON-RPC Proxy — Blast Mainnet

> QuickNode JSON-RPC Proxy — Blast Mainnet is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-14).

Proxies JSON-RPC calls to the Blast mainnet blockchain, enabling read and write operations on the Blast L2 network via standard Ethereum-compatible RPC methods.

## Facts

- Endpoint: POST https://x402.quicknode.com/blast-mainnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-4def1503
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eAY2537c3WW6ayuGoTKo2

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 quicknode-4def1503 -d '<json body>'
```

Example prompt: Call eth_getBalance on Blast mainnet for address 0xAbCd1234...5678 at the latest block — I need to check the current ETH balance of this wallet on Blast L2.

## When to prefer this

Use this endpoint when you need to interact specifically with the Blast mainnet L2 blockchain — querying balances, calling contracts, fetching blocks, or submitting transactions on Blast. Choose this over generic Ethereum endpoints when the target contract or wallet is deployed on Blast L2 rather than Ethereum mainnet or other chains.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array returns error code -32602 invalid params
- Network congestion may cause timeouts on eth_call or trace methods
- Payment failure (insufficient USDC balance) results in 402 Payment Required before the call is processed
- Unsupported methods specific to other chains (e.g. Solana-specific calls) will return errors

## How this service works

JSON-RPC proxy — blast-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result field with the requested blockchain data (e.g. block number as hex, balance in wei, transaction receipt object, contract return value) or an error object with code and message if the call failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "jsonrpc",
  "method"
 ],
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ],
   "description": "Request identifier"
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
  },
  "params": {
   "type": "array",
   "description": "Method parameters"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "error": {
   "type": "object",
   "properties": {
    "code": {
     "type": "integer"
    },
    "message": {
     "type": "string"
    }
   }
  },
  "result": {
   "description": "RPC result (type varies by method)"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-4def1503/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quicknode.com](https://www.zero.xyz/host/x402.quicknode.com/llms.txt)