# QuickNode JSON-RPC Proxy — peaq Mainnet

> QuickNode JSON-RPC Proxy — peaq 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 peaq mainnet blockchain network via QuickNode's infrastructure

## Facts

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

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

Example prompt: Call eth_blockNumber on the peaq mainnet to get the current block height.

## When to prefer this

Use this endpoint when you need direct JSON-RPC access to the peaq mainnet blockchain — particularly for DePIN, IoT identity, or machine economy use cases built on peaq. Prefer this over generic Ethereum RPC endpoints when the target contract or account is deployed specifically on peaq mainnet. Use QuickNode's infrastructure for reliable, low-latency access compared to public RPC endpoints.

## 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 timeout or slow response
- Payment failure (insufficient USDC or x402 handshake issue) blocks request entirely
- Unsupported peaq-specific RPC methods may return not-implemented errors

## How this service works

JSON-RPC proxy — peaq-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested blockchain method, such as block numbers, transaction hashes, account balances, contract call return values, or raw blockchain state — 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-7c6f40dd/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)