# QuickNode JSON-RPC Proxy — Polkadot Mainnet

> QuickNode JSON-RPC Proxy — Polkadot 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 method calls to the Polkadot (DOT) mainnet blockchain node via QuickNode infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/dot-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-20206f3f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iGI9szeU01NhSRgEYuSh6

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

Example prompt: Call the Polkadot mainnet RPC to get the latest finalized block hash using the chain_getFinalizedHead method.

## When to prefer this

Use this endpoint when you need to interact specifically with the Polkadot (DOT) mainnet blockchain via JSON-RPC, such as querying chain state, submitting extrinsics, or reading block and account data. Prefer this over self-hosted nodes for reliability and over other chain endpoints when the target network is Polkadot mainnet specifically.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array causes -32602 invalid params error
- Payment not provided or insufficient results in HTTP 402 Payment Required
- Network congestion or node unavailability causes timeout or 503 error
- Unsupported Polkadot-specific method returns error response

## How this service works

JSON-RPC proxy — dot-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested Polkadot mainnet RPC method, such as block headers, account storage, transaction receipts, or chain metadata, along with the matching request ID.

## 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-20206f3f/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)