# Pocket Network – Fraxtal JSON-RPC

> Pocket Network – Fraxtal JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Provides read-only Ethereum-compatible JSON-RPC access to the Fraxtal OP-Stack L2 blockchain, served by Pocket Network's decentralised node fleet, billed per-request in USDC.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/fraxtal?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-fraxtal-json-rpc-ad631934
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YpVDC0aCW5wuPL1-S9Fr_

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 pocket-network-fraxtal-json-rpc-ad631934 -d '<json body>'
```

Example prompt: What is the current ETH balance of wallet 0xAbC…1234 on Fraxtal? Use eth_getBalance with the latest block tag.

## When to prefer this

Choose this endpoint when you need trustless, decentralised, pay-per-use read access to the Fraxtal OP-Stack L2 without managing API keys or subscriptions. It is ideal for agents that make sporadic or unpredictable call volumes to Fraxtal and want to pay only for what they use in USDC. Prefer it over centralised RPC providers when decentralisation and censorship-resistance of the node layer matter, or when no account sign-up is acceptable.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Write methods (eth_sendRawTransaction) are not supported — returns error or is rejected
- Malformed params array returns error code -32602 (invalid params)
- Payment failure (insufficient USDC balance) results in HTTP 402 before the RPC call is made
- Node temporarily out of sync may return stale block data
- Rate or per-request payment processing delays can cause timeouts

## How this service works

Read-only JSON-RPC access to Fraxtal, the OP-Stack L2 by Frax, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

## Output

A standard Ethereum JSON-RPC response object containing a 'result' field with the requested on-chain data (balance in wei, block object, transaction receipt, encoded return value, etc.) or an 'error' object if the call failed. Responses reflect the current state of the Fraxtal OP-Stack L2 chain as seen by Pocket Network's decentralised supplier set.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "debug_getRawHeader",
    "debug_getRawReceipts",
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_config",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockAccessList",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "eth_getStorageValues",
    "eth_getTransactionByBlockHashAndIndex",
    "eth_getTransactionByBlockNumberAndIndex",
    "eth_getTransactionByHash",
    "eth_getTransactionCount",
    "eth_getTransactionReceipt",
    "eth_getUncleByBlockHashAndIndex",
    "eth_getUncleByBlockNumberAndIndex",
    "eth_getUncleCountByBlockHash",
    "eth_getUncleCountByBlockNumber",
    "eth_maxPriorityFeePerGas",
    "eth_newBlockFilter",
    "eth_newFilter",
    "eth_newPendingTransactionFilter",
    "eth_simulateV1",
    "eth_syncing",
    "eth_uninstallFilter",
    "net_listening",
    "net_peerCount",
    "net_version",
    "web3_clientVersion",
    "web3_sha3"
   ],
   "description": "JSON-RPC read method, e.g. eth_getBalance"
  },
  "params": {
   "description": "Parameters per the Ethereum JSON-RPC spec"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": 1,
   "result": false,
   "jsonrpc": "2.0"
  },
  "portal": {
   "serviceId": "fraxtal",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-fraxtal-json-rpc-ad631934/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)
