# AmanChain Bridge Status

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

Fetches the live on-chain status of a cross-chain bridge on AmanChain, executed deterministically against real consensus state.

## Facts

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

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-bridge-status-c984547f -d '<json body>'
```

Example prompt: Can you check the current live status of the AmanChain bridge — I want to know if it's operational and what the bridge health looks like right now?

## When to prefer this

Choose this endpoint when you need deterministic, consensus-verified bridge status data directly from an AmanChain node — not aggregated or cached third-party data. Best for pre-transfer health checks, real-time monitoring of cross-chain bridge operations, or verifying bridge liquidity before executing DeFi actions on AmanChain. Prefer over generic block explorers when you need structured, machine-readable bridge state without API key setup.

## Known failure modes

- Bridge service temporarily unavailable — node may be syncing or behind consensus
- Invalid or malformed request input — serviceId must be exactly 'aman-bridge-status'
- Payment not settled — x402 USDC payment on Base required before response is returned
- Network congestion causing delayed consensus state response
- Unknown bridge state if chain is undergoing a hard fork or network upgrade

## How this service works

Bridge Status: 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-bridge-status","request":"<input>"}. No account, no API key.

## Output

Returns the live on-chain bridge status for AmanChain, including operational state, pool balances, and consensus-verified health metrics for the bridge, executed deterministically against real blocks.

## 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-bridge-status-c984547f/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)