# ChainHilt Bridge Status Lookup

> ChainHilt Bridge Status Lookup is a paid API for AI agents from chainhilt.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-16).

Poll the status of an in-flight cross-chain bridge transfer by adapter type, source chain, and transaction hash until it reaches a terminal state.

## Facts

- Endpoint: GET https://chainhilt.ai/api/v1/bridge/status?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainhilt-bridge-status-lookup-da88ecea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rcTkkR9jM9as1vOPG4IE-

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 chainhilt-bridge-status-lookup-da88ecea
```

Example prompt: Check the status of my Across bridge transfer on Ethereum mainnet (chain ID 1) with tx hash 0xa7d9fe3e3110c7f2d534069ed93ea4326ec05c450831dfeabe2342b9f65049d1 — keep polling every 10 seconds until it shows filled, refunded, or failed.

## When to prefer this

Use this endpoint after calling chainhilt bridge/execute to track the resulting cross-chain transfer to completion. It supports all major adapters (Across, Circle CCTP, deBridge, LayerZero, Relay, Socket) in a unified interface, making it the right choice when your agent needs a single polling loop across any adapter rather than integrating each bridge provider's native status API separately.

## Known failure modes

- not_found status returned when provider hasn't indexed the transaction yet (normal for up to ~1 minute after send)
- 429 rate limit — wait the Retry-After header duration before retrying (not billed)
- providerRef missing or wrong for layerzero/relay adapters causes persistent not_found
- invalid txHash format rejected by schema validation
- failed status with detail field explaining irrecoverable error
- refunded status indicating funds returned to sender without delivery

## How this service works

Look up a bridge after its transaction was sent, by the adapter that built it and the hash of the bridge transaction on the source chain; layerzero and relay also need the providerRef that bridge/execute returned (0x and 64 hex characters). Poll it every 10 to 15 seconds until the status is filled, refunded or failed; an error answer, such as a 429, is not charged. After a 429, wait the Retry-After seconds.

## Output

Returns a JSON object with the bridge adapter name, a normalized status enum (not_found, pending, filled, refund_pending, refunded, failed), the target chain transaction hash once available, the raw provider status string, and an optional detail field explaining failures, refunds, or recovery options.

## 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"
    },
    "queryParams": {
     "type": "object",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "adapter",
      "sourceChainId",
      "txHash"
     ],
     "properties": {
      "txHash": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{64}$",
       "description": "Hash of the bridge transaction on the source chain (the last execute action, not the approval)."
      },
      "adapter": {
       "enum": [
        "across",
        "circleCctp",
        "debridge",
        "layerzero",
        "relay",
        "socket"
       ],
       "type": "string",
       "description": "The adapter that built the bridge: adapterId from bridge/execute."
      },
      "providerRef": {
       "type": "string",
       "minLength": 1,
       "description": "The route's providerRef from bridge/execute. Required for layerzero and relay, which look the transfer up by this id."
      },
      "sourceChainId": {
       "type": "integer",
       "description": "EVM chain id the bridge transaction was sent on.",
       "exclusiveMinimum": 0
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "adapter",
      "status"
     ],
     "properties": {
      "detail": {
       "type": "string",
       "description": "What the provider reports beyond the status: why it failed, where a refund went, or how funds can still be recovered. Show it to the user."
      },
      "status": {
       "enum": [
        "not_found",
        "pending",
        "filled",
        "refund_pending",
        "refunded",
        "failed"
       ],
       "type": "string",
       "description": "not_found: the provider has not indexed the transaction yet, which is normal for up to a minute after sending; for layerzero and relay, one that lasts means providerRef is not from the execute whose transaction was sent. pending: on 
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "filled",
  "adapter": "circleCctp",
  "targetTxHash": "0xa7d9fe3e3110c7f2d534069ed93ea4326ec05c450831dfeabe2342b9f65049d1",
  "providerStatus": "COMPLETE"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainhilt-bridge-status-lookup-da88ecea/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainhilt.ai](https://www.zero.xyz/host/chainhilt.ai/llms.txt)
