# QuickNode JSON-RPC Proxy — Injective Testnet

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

Proxies JSON-RPC calls to the Injective testnet blockchain node via QuickNode infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/injective-testnet/
- 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-686eeb66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f8stcM3XLKoOSN9vNsdNV

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

Example prompt: Call eth_blockNumber on the Injective testnet via QuickNode and tell me the current block height — use jsonrpc 2.0 with request id 1.

## When to prefer this

Choose this endpoint when you need to interact with the Injective testnet specifically — for development, testing, or staging workflows involving Injective Protocol smart contracts or chain state. Prefer this over mainnet endpoints when testing new contract deployments or transaction flows without real financial risk.

## Known failure modes

- Invalid or unsupported JSON-RPC method returns an error object with code and message
- Malformed params array causes parse or invalid params error
- Payment not included or insufficient USDC ($10 required per call) results in 402 Payment Required
- Network or node unavailability returns a 5xx error
- Testnet node may lag behind or have gaps compared to mainnet

## How this service works

JSON-RPC proxy — injective-testnet

## Output

A JSON-RPC response object containing the result field with blockchain data (e.g. block number, transaction receipt, contract return value) or an error object if the method call failed. The response mirrors standard JSON-RPC 2.0 format with matching id and jsonrpc fields.

## 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-686eeb66/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)