# three.ws Cross-Chain Bridge Status

> three.ws Cross-Chain Bridge Status is a paid API for AI agents from three.ws, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-11).

Returns real-time operational status and latency for major cross-chain bridges (Wormhole, Li.Fi, deBridge) with a confidence-weighted signal.

## Facts

- Endpoint: POST https://three.ws/api/x402/cross-chain?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-cross-chain-bridge-status-7caf36c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cpPOouLFQfzXRYs2kRBUQ

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 three-ws-cross-chain-bridge-status-7caf36c9 -d '<json body>'
```

Example prompt: Check the current status of all major cross-chain bridges — Wormhole, Li.Fi, and deBridge — and tell me if any are degraded or down before I send tokens across chains.

## When to prefer this

Choose this endpoint when an agent needs a quick, pre-transfer sanity check on cross-chain bridge health before routing tokens or executing DeFi operations. It is ideal when you want a single aggregated view across Wormhole, Li.Fi, and deBridge rather than querying each provider individually. Prefer this over manual provider checks when latency data and a confidence-weighted signal are needed for automated decision-making.

## Known failure modes

- Payment not included or invalid — returns HTTP 402 requiring USDC micropayment
- Upstream bridge status providers (WormholeScan, Li.Fi, dln.trade) are unreachable — may return stale or partial data
- Unsupported mode value — only 'bridge_status' is accepted; other values will be rejected
- Network timeout from one or more upstream providers may reduce confidence score or mark bridge as unknown

## How this service works

Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.

## Output

Returns a JSON object with a timestamp, overall signal (neutral/up/down), per-bridge entries showing chain name, operational status, provider source, and latency in milliseconds, plus a plain-English headline, a confidence score (0–1), and a count of bridges currently down.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "bridge_status"
   ],
   "type": "string",
   "default": "bridge_status",
   "description": "Operation mode. Only \"bridge_status\" is supported."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ts": "2026-06-28T12:00:00Z",
  "mode": "bridge_status",
  "signal": "neutral",
  "bridges": [
   {
    "chain": "wormhole",
    "status": "operational",
    "provider": "wormholescan",
    "latency_ms": 210
   },
   {
    "chain": "lifi",
    "status": "operational",
    "provider": "li.fi",
    "latency_ms": 334
   },
   {
    "chain": "debridge",
    "status": "degraded",
    "provider": "dln.trade",
    "latency_ms": 1870
   }
  ],
  "headline": "All Solana bridges operational",
  "confidence": 0.82,
  "down_count": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-cross-chain-bridge-status-7caf36c9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from three.ws](https://www.zero.xyz/host/three.ws/llms.txt)