# QuickNode JSON-RPC Proxy — Injective Mainnet

> QuickNode JSON-RPC Proxy — Injective 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 method calls to the Injective mainnet blockchain node via QuickNode infrastructure

## Facts

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

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

Example prompt: Call eth_blockNumber on the Injective mainnet using QuickNode's JSON-RPC proxy and tell me the current block height.

## When to prefer this

Use this endpoint when you need programmatic access to Injective mainnet blockchain data or need to broadcast transactions to Injective. Prefer this over generic Ethereum RPC endpoints when working specifically with Injective's EVM-compatible or Cosmos-based APIs. Useful when QuickNode's high-availability infrastructure is needed for production-grade reliability.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array causes -32602 invalid params error
- Payment not fulfilled results in 402 Payment Required response
- Node unavailable or overloaded may return 503 or timeout
- Unsupported method for Injective network returns error

## How this service works

JSON-RPC proxy — injective-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested blockchain method call — e.g. block number, transaction data, account balance, contract state, or broadcast confirmation — along with the matching request id and jsonrpc version field.

## 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-b3ea35df/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)