# QuickNode NEAR Mainnet JSON-RPC Proxy

> QuickNode NEAR Mainnet JSON-RPC Proxy 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 NEAR Protocol mainnet blockchain via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/near-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-1cc1c51c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jk782oVQ_-uLERU6PsZem

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

Example prompt: Can you call the NEAR mainnet RPC and get the current block height using the block method with finality set to final?

## When to prefer this

Use this endpoint when you need direct, low-latency JSON-RPC access to the NEAR Protocol mainnet. Prefer this over generic NEAR RPC endpoints when you need QuickNode's reliable infrastructure and are willing to pay per-call via x402. Best suited for querying account state, fetching blocks, calling view functions, or broadcasting signed transactions on NEAR mainnet.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601
- Malformed params array causes error code -32602
- Network unavailability returns HTTP 503
- Payment not included or insufficient triggers HTTP 402
- Rate limiting may return HTTP 429

## How this service works

JSON-RPC proxy — near-mainnet

## Output

Returns a JSON-RPC 2.0 response object containing the result of the requested NEAR Protocol method call, such as block details, account state, transaction receipts, or contract view results. Errors are returned as standard JSON-RPC error objects.

## 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-1cc1c51c/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)