# QuickNode JSON-RPC Proxy — Redstone Mainnet

> QuickNode JSON-RPC Proxy — Redstone 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 Redstone blockchain mainnet, enabling on-chain reads and writes via standard Ethereum-compatible RPC methods

## Facts

- Endpoint: POST https://x402.quicknode.com/redstone-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-2d7bd8b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zyD94sVAQrXJTruyulLvB

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

Example prompt: Call eth_blockNumber on the Redstone mainnet to get the latest block number — use JSON-RPC 2.0 with an empty params array and request ID 1.

## When to prefer this

Use this endpoint when you specifically need to interact with the Redstone mainnet blockchain via standard Ethereum JSON-RPC. Choose this over generic alternatives when you need QuickNode's reliable node infrastructure for Redstone specifically, as opposed to other chains like Mantle, Worldchain, or NEAR which have separate sibling endpoints.

## Known failure modes

- Invalid or unsupported JSON-RPC method returns a method-not-found error
- Malformed params array causes an invalid-params error
- Payment not included or insufficient USDC results in HTTP 402 rejection
- Network or node unavailability returns a server error or timeout
- Contract reverts return execution error in the result

## How this service works

JSON-RPC proxy — redstone-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number, account balance, contract return value, transaction receipt) or a JSON-RPC error object if the call fails.

## 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-2d7bd8b6/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)