# QuickNode JSON-RPC Proxy — Morph Mainnet

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

## Facts

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

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

Example prompt: Can you call eth_blockNumber on Morph mainnet to get the current block height?

## When to prefer this

Use this endpoint when you specifically need to interact with the Morph mainnet blockchain via standard Ethereum JSON-RPC. Prefer this over generic alternatives when you need a reliable, hosted RPC node for Morph without running your own infrastructure. QuickNode's endpoint is particularly suitable for agents that need fast, pay-per-call access without API key management.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code -32601
- Malformed params array causes -32602 invalid params error
- Payment not completed results in 402 Payment Required before RPC is processed
- Network congestion or node downtime may return 503 or timeout
- Unsupported method for Morph chain returns method not found error

## How this service works

JSON-RPC proxy — morph-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number, account balance, transaction data, contract return value) or an error object with code and message 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-fcef850c/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)