# Bridge Status Tracker

> Bridge Status Tracker is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-16).

Tracks the completion status of a cross-chain bridge transfer using its source transaction hash via the LiFi status API.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/bridge-status?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bridge-status-tracker-5c2914cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NFgPGPCW8HNb-DcO_5uQa

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 bridge-status-tracker-5c2914cc
```

Example prompt: Can you check if my bridge transfer has completed? The source tx hash is 0xabc123... and it was going from Ethereum to Base.

## When to prefer this

Use this endpoint when an agent has already initiated a cross-chain bridge transfer and needs to confirm its outcome. It is the natural complement to a bridge-route/initiate endpoint. Prefer this over general blockchain explorers when you need a normalized status (completed/pending/failed) rather than raw transaction data, and when you need the destination-chain receiving tx hash. Pass optional from/to/bridge parameters for faster lookups.

## Known failure modes

- txHash not yet indexed returns 'not-found' — should be retried after a short delay, not treated as failure
- Invalid or non-bridge txHash returns 'not-found' permanently
- Missing required txHash parameter causes a bad request error
- Network or LiFi API downtime may cause upstream errors

## How this service works

The other half of bridge-route. A bridge takes minutes with funds in flight, and from the source chain alone an agent cannot tell if it completed. Tracks a transfer by its source tx hash via the LiFi status API: completed (with the receiving tx), pending (poll again), failed (with the reason), or not-found (not a bridge tx, or too early to index). Pass from/to/bridge for a faster lookup. not-found reads as 'not indexed yet', never 'failed'. Not financial advice.

## Output

Returns one of four statuses: 'completed' (with the destination chain receiving tx hash), 'pending' (transfer still in flight, poll again later), 'failed' (with a reason string explaining what went wrong), or 'not-found' (transfer not yet indexed — not a failure, just too early).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "txHash"
     ],
     "properties": {
      "to": {
       "type": "string",
       "description": "To chain (optional)"
      },
      "from": {
       "type": "string",
       "description": "From chain (optional)"
      },
      "txHash": {
       "type": "string",
       "description": "Source-chain tx hash"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bridge-status-tracker-5c2914cc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)