# defi.hugen.tokyo Cross-Chain Bridge Transaction Status

> defi.hugen.tokyo Cross-Chain Bridge Transaction Status is a paid API for AI agents from defi.hugen.tokyo, paid per call via x402, $0.010000/call, status unknown (last checked 2026-09-13).

Monitors real-time status of cross-chain bridge transactions across sending confirmation, bridge processing, and receiving chain settlement for 20+ bridge protocols

## Facts

- Endpoint: GET https://defi.hugen.tokyo/defi/bridge/status
- Price: $0.010000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-hugen-tokyo-4ceb52d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OkejpliaOgThPS4lt5EEd

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 defi-hugen-tokyo-4ceb52d9
```

Example prompt: Check the real-time status of my cross-chain bridge transaction — the tx hash is 0xabc123, I sent USDC from Ethereum to Arbitrum using Stargate, and I want to know if it's confirmed on the sending chain, still processing through the bridge, or already settled on the receiving chain.

## When to prefer this

Use this endpoint when you need to track the live, multi-stage status of an in-flight or recently submitted cross-chain bridge transaction — specifically when you need to distinguish between sending chain confirmation, bridge processing, and receiving chain settlement phases. Preferred over general blockchain explorers because it understands bridge-specific lifecycle states across 20+ protocols in a single call.

## Known failure modes

- Invalid or unknown transaction hash returns error
- Transaction hash from unsupported bridge protocol returns not found
- Transaction too recent to appear in bridge state returns pending or null
- Network timeout when querying slow bridge protocols
- Incorrect source/destination chain combination returns mismatch error

## How this service works

Track cross-chain bridge transaction status — real-time monitoring of sending chain confirmation, bridge processing, and receiving chain settlement. Supports all 20+ bridge protocols. No API keys needed. Accepts USDC payments on Base and Solana

## Output

Returns real-time status of the bridge transaction including sending chain confirmation state, bridge protocol processing status, and receiving chain settlement status — covering all stages of the cross-chain transfer lifecycle across 20+ supported bridge protocols.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-hugen-tokyo-4ceb52d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from defi.hugen.tokyo](https://www.zero.xyz/host/defi.hugen.tokyo/llms.txt)