# HALOWERK kettenwerk Transaction Status

> HALOWERK kettenwerk Transaction Status is a paid API for AI agents from kette.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Checks whether an EVM transaction succeeded, is pending, or is unknown, and reports finality status with chain-specific block confirmation rules and gas cost

## Facts

- Endpoint: POST https://kette.halowerk.com/tx/status
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-kettenwerk-transaction-status-e492e0e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GylssbSbHI3xH68cj9uGW

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-transaction-status-e492e0e7 -d '<json body>'
```

Example prompt: Can you check if my Ethereum transaction 0x4a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789ab went through and whether it's final yet?

## When to prefer this

Use this endpoint when you need authoritative, chain-aware transaction status with proper finality semantics across Ethereum, Base, Arbitrum, Optimism, Polygon, or BNB Smart Chain. Unlike generic block explorers, it explicitly models the difference between 'unknown' and 'failed', applies chain-specific finality rules rather than a single hard-coded confirmation count, and returns gas cost alongside status — making it suitable for agents that need to reason about transaction outcomes before proceeding with dependent actions.

## Known failure modes

- Transaction hash not found on any node — reported as 'unbekannt' (unknown), never as failed
- Invalid chain identifier supplied — returns validation error
- Malformed transaction hash (not 0x + 64 hex chars) — schema validation error
- Node connectivity issues causing incomplete finality data
- Very recent transactions may show as pending before first confirmation

## How this service works

Reads one transaction hash on Ethereum, Base, Arbitrum, Optimism, Polygon or BNB Smart Chain and answers the question an agent actually has: did it go through, is it final yet, and what did it cost. Finality is defined differently per chain, so the rule used and the required block count are part of the answer instead of a single hard-coded number. A hash that no node knows is reported as "unbekannt", never as "fehlgeschlagen" — the two are not the same. A pending transaction whose nonce has alre

## Output

Returns the transaction's execution status (success, failed, pending, or unknown), its finality status with the chain-specific confirmation rule and required block count, and the gas cost paid. Distinguishes clearly between a hash unknown to any node versus a failed transaction, and flags pending transactions whose nonce has already been replaced.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "arbitrum",
    "optimism",
    "polygon",
    "bsc"
   ],
   "type": "string",
   "description": "Chain the transaction lives on."
  },
  "tx_hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Transaction hash, 0x plus 64 hex characters."
  }
 }
}
```

## More

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