# QuickNode JSON-RPC Proxy — Ink Mainnet

> QuickNode JSON-RPC Proxy — Ink 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 Ink blockchain mainnet, enabling eth-compatible RPC methods such as eth_blockNumber, eth_call, eth_getBalance, and more.

## Facts

- Endpoint: POST https://x402.quicknode.com/ink-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-e7da2932
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JH36OPyw_dDhUCrmIo4xd

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-e7da2932 -d '<json body>'
```

Example prompt: Can you call eth_getBalance on the Ink mainnet for wallet address 0xAbC123... and tell me the current balance?

## When to prefer this

Use this endpoint when you need to interact with the Ink mainnet blockchain specifically via standard Ethereum-compatible JSON-RPC methods. Prefer this over generic RPC providers when you need reliable, paid-tier access to Ink mainnet with QuickNode's infrastructure quality.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array returns error code -32602 invalid params
- Payment not provided or insufficient USDC results in 402 Payment Required
- Network congestion may cause timeouts on long-running eth_call operations
- Requesting data for a block that doesn't exist returns null result

## How this service works

JSON-RPC proxy — ink-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number as hex, balance in wei, contract return data) or an error object with code and message if the call fails.

## 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-e7da2932/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)