# AmanChain Pool Analytics

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

Fetches on-chain liquidity pool analytics from the AmanChain DEX, executed deterministically against live consensus state and paid per call via x402 in USDC.

## Facts

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

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-pool-analytics-54da890a -d '<json body>'
```

Example prompt: Can you pull the on-chain pool analytics for the main USDC/ETH liquidity pool on AmanChain — I want to see TVL, volume, and current balances?

## When to prefer this

Choose this endpoint when you need deterministic, real-time on-chain pool analytics from AmanChain's DEX executed directly against live consensus state — particularly when trust in the data source matters and you want verifiable on-chain execution rather than a third-party aggregator's cached or estimated figures. Best suited for agents operating in DeFi workflows where live pool state (reserves, TVL, volume) is critical.

## Known failure modes

- Invalid or unrecognized pool identifier returns an error or empty result
- Network congestion or node unavailability may cause delayed or failed responses
- Insufficient USDC balance for x402 payment results in a 402 Payment Required error
- Malformed JSON request body (missing serviceId or request fields) returns a validation error
- Pool not found on AmanChain returns a not-found or null result

## How this service works

Pool Analytics: 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-pool-analytics","request":"<input>"}. No account, no API key.

## Output

Returns on-chain pool analytics data executed against live AmanChain consensus state, including metrics such as pool token balances, total value locked (TVL), trading volume, liquidity depth, fee data, and other DEX pool statistics specific to the queried pool.

## 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-pool-analytics-54da890a/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)
