# AmanChain Network Statistics

> AmanChain Network Statistics is a paid API for AI agents from preview-chat-c6089071-758a-449d-b4a7-6fa19ebc955c.space-z.ai, paid per call via x402, $0.003732/call, status unknown (last checked 2026-09-13).

Retrieves live AmanChain blockchain network statistics from on-chain consensus state, including node counts, block metrics, pool data, and network health indicators.

## Facts

- Endpoint: POST https://preview-chat-c6089071-758a-449d-b4a7-6fa19ebc955c.space-z.ai/api/x402/aman-network-stats
- Price: $0.003732/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/amanchain-network-statistics-15cc83f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZhwywUh-ZsghZN8vr8rDt

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 amanchain-network-statistics-15cc83f5 -d '<json body>'
```

Example prompt: Can you pull the live AmanChain network statistics right now — things like block height, node count, and overall network health?

## When to prefer this

Choose this endpoint when you need live, deterministically executed AmanChain blockchain network statistics sourced directly from on-chain consensus state with no API key required — ideal for agents monitoring AmanChain infrastructure health, validating network conditions before executing swaps, or building dashboards around AmanChain node and block metrics. Prefer this over off-chain data aggregators when on-chain accuracy and determinism are required.

## Known failure modes

- Payment not settled — x402 USDC payment on Base must succeed before the call is processed
- Invalid serviceId — must be exactly 'aman-network-stats'
- Node unavailable or consensus state temporarily inaccessible, returning a service error
- Malformed JSON body causing a 400 bad request
- Network congestion on Base causing payment settlement delay

## How this service works

Network Statistics: node-operated on-chain service Executed deterministically by the AmanChain node against live consensus state (real blocks, pools, balances) — paid per call via x402, settled in USDC on Base. Input: JSON body {"serviceId":"aman-network-stats","request":"<input>"}. No account, no API key.

## Output

Returns live AmanChain network statistics derived from real on-chain consensus state, including metrics such as active node count, current block height, transaction throughput, pool statistics, and overall network health indicators, as executed deterministically by an AmanChain node.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "body": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "object",
     "example": {
      "ok": true
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/amanchain-network-statistics-15cc83f5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from preview-chat-c6089071-758a-449d-b4a7-6fa19ebc955c.space-z.ai](https://www.zero.xyz/host/preview-chat-c6089071-758a-449d-b4a7-6fa19ebc955c.space-z.ai/llms.txt)