# AmanChain Holder Distribution Stats

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

Returns on-chain token holder distribution statistics for a given token on the AmanChain network, executed deterministically against live consensus state.

## Facts

- Endpoint: POST https://preview-chat-c6089071-758a-449d-b4a7-6fa19ebc955c.space-z.ai/api/x402/aman-holder-stats
- Price: $0.012441/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/amanchain-holder-distribution-stats-8269e34b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KQhmyZC8kWFxj0dcg87Ky

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-holder-distribution-stats-8269e34b -d '<json body>'
```

Example prompt: Pull the holder distribution stats for the AmanChain token with address 0xABC123 — I want to see how concentrated the supply is and how many wallets are holding it.

## When to prefer this

Use this endpoint when you need real-time, deterministic holder distribution data for tokens on the AmanChain network. It is ideal for decentralization audits, whale concentration checks, and pre-investment due diligence on AMT-20 tokens. Prefer it over generic blockchain explorers when you need structured, machine-readable holder stats paid per-call without API key setup.

## Known failure modes

- Invalid or unknown token address returns an error or empty result
- Malformed request string causes a parsing error
- Node sync lag may produce slightly stale data during chain reorganizations
- Payment failure via x402/USDC causes request rejection before execution
- Missing or incorrect serviceId field causes routing failure

## How this service works

Holder Distribution: 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-holder-stats","request":"<input>"}. No account, no API key.

## Output

Returns on-chain holder distribution data including number of unique holders, supply concentration metrics (e.g. top-N wallet percentages), individual holder balances or ranges, and distribution breakdowns — all sourced deterministically from live AmanChain consensus state.

## 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-holder-distribution-stats-8269e34b/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)