# HALOWERK kettenwerk Bridge Transaction Tracker

> HALOWERK kettenwerk Bridge Transaction Tracker is a paid API for AI agents from kette.netzhandwerker.de, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-13).

Tracks a cross-chain bridge deposit transaction by hash and source chain, returning bridging status information.

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/bridge/track
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-kettenwerk-bridge-transaction-tracker-bf5e197e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3_xRQultvKxrXR87DyB_y

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 halowerk-kettenwerk-bridge-transaction-tracker-bf5e197e -d '<json body>'
```

Example prompt: Can you track my bridge deposit on Arbitrum with transaction hash 0x4a2b8c...def1 and let me know if it went through? The bridge used was Stargate.

## When to prefer this

Use this endpoint when you need to look up or verify the status of a specific cross-chain bridge deposit and have the transaction hash available. Prefer this over generic blockchain explorers when you specifically need bridge-aware tracking that can identify the bridge protocol and report deposit confirmation status on supported chains via the HALOWERK kettenwerk service.

## Known failure modes

- Invalid or malformed tx_hash (not 0x + 64 hex chars) returns an error
- Unrecognized source_chain value may cause lookup failure
- Transaction not yet indexed returns pending or not-found status
- Bridge auto-detection failure without a bridge hint may return an ambiguous result
- Network or RPC errors on the source chain may cause timeouts

## How this service works

HALOWERK kettenwerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

Returns the tracking status and bridging details for the submitted deposit transaction, including confirmation state and bridge identification. If auto-detection fails, the optional bridge hint is used to resolve the provider.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bridge": {
   "type": "string",
   "description": "Optional hint which bridge was used. Only used when detection fails."
  },
  "tx_hash": {
   "type": "string",
   "description": "Transaction hash of the deposit, 0x followed by 64 hex characters."
  },
  "source_chain": {
   "type": "string",
   "description": "Chain the deposit was made on."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-kettenwerk-bridge-transaction-tracker-bf5e197e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kette.netzhandwerker.de](https://www.zero.xyz/host/kette.netzhandwerker.de/llms.txt)