# QuickNode JSON-RPC Proxy — Lens Mainnet

> QuickNode JSON-RPC Proxy — Lens 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).

Routes JSON-RPC calls to the Lens Protocol mainnet blockchain via QuickNode's node infrastructure

## Facts

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

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

Example prompt: Call eth_blockNumber on the Lens mainnet using QuickNode's RPC — I need to know the current block height right now.

## When to prefer this

Use this endpoint when you need to interact specifically with the Lens Protocol mainnet blockchain — reading contract state, querying balances, fetching blocks, or broadcasting transactions on the Lens network. Prefer this over generic Ethereum endpoints when the target contract or account lives on Lens mainnet rather than Ethereum or other EVM chains.

## Known failure modes

- Invalid JSON-RPC method returns error code -32601 (method not found)
- Malformed params array causes -32602 (invalid params)
- Insufficient payment (HTTP 402) if USDC payment not included
- Network or node unavailability returns HTTP 503
- Invalid jsonrpc version causes parse error -32700

## How this service works

JSON-RPC proxy — lens-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number, transaction receipt, call return value) or an error object with code and message if the call failed.

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