# QuickNode JSON-RPC Proxy — Tempo Testnet

> QuickNode JSON-RPC Proxy — Tempo Testnet is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-13).

Proxies JSON-RPC calls to the Tempo testnet blockchain via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/tempo-testnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-4b4e09ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o8yT1L21aBerppUus-UNf

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

Example prompt: Call eth_blockNumber on the Tempo testnet using QuickNode's RPC proxy so I can see the latest block height.

## When to prefer this

Use this endpoint when you need to interact specifically with the Tempo testnet blockchain via standard JSON-RPC methods (eth_*, net_*, web3_*). Prefer this over other QuickNode endpoints when testing contracts or transactions on Tempo testnet specifically, rather than mainnet or other testnets like Ethereum Sepolia or Kaia Kairos.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code -32601
- Malformed params array causes -32602 invalid params error
- Network unavailable returns HTTP 503 or connection timeout
- Payment not provided or insufficient returns HTTP 402 Payment Required
- Unsupported method for Tempo testnet returns method not found error

## How this service works

JSON-RPC proxy — tempo-testnet

## 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-4b4e09ef/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)