# QuickNode JSON-RPC Proxy — Sei Pacific

> QuickNode JSON-RPC Proxy — Sei Pacific 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 Sei Pacific (sei-pacific) blockchain network via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/sei-pacific/
- 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-d934e305
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AM-P23tvWnehh_a2rA2uq

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

Example prompt: What is the current block number on the Sei Pacific mainnet? Use the eth_blockNumber JSON-RPC method to check.

## When to prefer this

Use this endpoint when you need direct JSON-RPC access to the Sei Pacific blockchain specifically — for reading chain state, submitting transactions, or calling smart contracts on the Sei network. Prefer this over alternatives when you need QuickNode's reliable node infrastructure for Sei and can pay per-call in USDC via x402.

## Known failure modes

- Invalid JSON-RPC method name returns an error response with code -32601
- Malformed params array causes a -32602 invalid params error
- Payment not included or insufficient USDC causes 402 Payment Required
- Network congestion or node unavailability returns a 503 or timeout
- Querying non-existent transaction hash returns null result

## How this service works

JSON-RPC proxy — sei-pacific

## Output

A JSON-RPC 2.0 response object containing the result of the requested blockchain method call — e.g. block number, transaction receipt, contract return value, account balance, or other chain state data — keyed to the original request ID.

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