# QuikNode Base Mainnet JSON-RPC (x402 Pay-Per-Request)

> QuikNode Base Mainnet JSON-RPC (x402 Pay-Per-Request) is a paid API for AI agents from x402.quiknode-cf.pro, paid per call via x402, $10/call, status unknown (last checked 2026-09-14).

Provides paid JSON-RPC access to the Base mainnet blockchain via QuikNode, supporting per-request micropayments using x402 protocol

## Facts

- Endpoint: POST https://x402.quiknode-cf.pro/base-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/x402-quiknode-cf-pro-f971650c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gasqr50dLTl-GRYy72GIu

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 x402-quiknode-cf-pro-f971650c -d '<json body>'
```

Example prompt: Can you check the current block number on Base mainnet using eth_blockNumber — I need to confirm the chain is synced before I do anything else?

## When to prefer this

Choose this endpoint when you need reliable, high-performance JSON-RPC access to Base mainnet and want pay-per-request pricing via x402 micropayments rather than a subscription. Ideal for agents making sporadic or bursty RPC calls where nanopayment ($0.0001/req via Circle Gateway) or per-request ($0.001/req) billing fits better than a monthly plan. Prefer over generic public RPC endpoints when uptime and throughput guarantees matter.

## Known failure modes

- Payment not provided or insufficient — 402 Payment Required with pricing details
- Invalid JSON-RPC method name — returns JSON-RPC error code -32601 Method not found
- Malformed params array — returns JSON-RPC error code -32602 Invalid params
- Node unavailable or overloaded — 503 Service Unavailable
- Auth failure with SIWX credit drawdown — 401 Unauthorized
- Rate limit exceeded — 429 Too Many Requests

## How this service works

Payment for Quicknode RPC access. Options: per-request ($0.001/request), nanopayment ($0.0001/request via Circle Gateway), or credit drawdown with SIWX authentication.

## Output

A JSON-RPC 2.0 response object containing the result of the requested Ethereum method call (e.g. block number as hex string, transaction receipt object, contract return data, balance in wei), or an error object if the call failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-quiknode-cf-pro-f971650c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quiknode-cf.pro](https://www.zero.xyz/host/x402.quiknode-cf.pro/llms.txt)