# Pocket Network – Oasys Hub-Layer Mainnet JSON-RPC

> Pocket Network – Oasys Hub-Layer Mainnet 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-03).

Provides read-only Ethereum JSON-RPC access to the Oasys Hub-Layer mainnet via Pocket Network's decentralised node supplier set, paid per-request in USDC.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/oasys?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-oasys-hub-layer-mainnet-json-rpc-614fab13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_janiHaid3rY9X5X9KkxYM

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-oasys-hub-layer-mainnet-json-rpc-614fab13 -d '<json body>'
```

Example prompt: What's the current OAS balance of wallet 0xABC123... on the Oasys Hub-Layer mainnet? Use eth_getBalance to check it.

## When to prefer this

Choose this endpoint when you need read-only EVM JSON-RPC access specifically to the Oasys Hub-Layer mainnet (chain ID 248) without setting up an API key or account — particularly suited for agents that can pay per-request in USDC via the x402 protocol and want the redundancy of Pocket Network's decentralised supplier set rather than a single centralised node provider.

## Known failure modes

- Invalid JSON-RPC method name returns an error object with code -32601
- Malformed params cause a -32602 invalid params error
- Write methods (eth_sendRawTransaction) are rejected as this is a read-only endpoint
- Payment failure or insufficient USDC balance blocks the request via x402 payment protocol
- Node sync lag may return slightly stale data for very recent blocks
- Rate-limit or supplier-set unavailability may cause transient 503 errors

## How this service works

Read-only JSON-RPC access to the Oasys Hub-Layer mainnet, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

## Output

Returns standard Ethereum JSON-RPC responses: block objects, transaction objects, account balances in wei, smart contract call return values, gas estimates, fee history arrays, transaction receipts, event logs, and other chain state data — all scoped to the Oasys Hub-Layer mainnet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "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": "oasys",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-oasys-hub-layer-mainnet-json-rpc-614fab13/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)