# QuickNode JSON-RPC Proxy — Abstract Mainnet

> QuickNode JSON-RPC Proxy — Abstract 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 Abstract blockchain mainnet, enabling agents to query chain state, submit transactions, and interact with smart contracts.

## Facts

- Endpoint: POST https://x402.quicknode.com/abstract-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-15f43fb6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BNyaUyHJJ-7NI2VAEmKZh

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

Example prompt: Using QuickNode's Abstract mainnet RPC, call eth_blockNumber on Abstract mainnet to get the latest block number.

## When to prefer this

Choose this endpoint when you need to interact specifically with the Abstract mainnet blockchain via standard Ethereum JSON-RPC interface, and you are willing to pay per-call via x402 micropayment protocol. Prefer this over self-hosted nodes when you need reliable, managed RPC access without infrastructure overhead.

## 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 timeouts
- Insufficient x402 payment ($10 USDC required) results in 402 Payment Required
- Node unavailability returns 503 Service Unavailable

## How this service works

JSON-RPC proxy — abstract-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result field with the requested chain data (e.g. block number as hex, transaction receipt object, eth_call return data), 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-15f43fb6/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)