# HALOWERK kettenwerk Transaction Status

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

Looks up the current status of a blockchain transaction by hash across major EVM-compatible chains

## Facts

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

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-c6fdc1fa -d '<json body>'
```

Example prompt: Can you check whether transaction 0x4f3a...c72b on the Base network has been confirmed yet?

## When to prefer this

Use this endpoint when you need a quick, paid-per-call lookup of a specific EVM transaction status across Ethereum, Base, Arbitrum, Optimism, Polygon, or BSC without maintaining your own RPC infrastructure. Particularly useful for agents that only occasionally need on-chain tx verification and prefer pay-per-use over subscription RPC plans.

## Known failure modes

- Invalid tx_hash format (not matching 0x + 64 hex chars) results in a validation error
- Chain not supported or misspelled returns an error
- Transaction hash does not exist on the specified chain returns not-found
- Network connectivity issues to the target chain's RPC may cause timeouts
- Payment failure via x402 protocol prevents the request from being processed

## How this service works

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

## Output

Returns the current status of the specified transaction on the given chain — typically including whether it is pending, confirmed, or failed, along with relevant confirmation metadata such as block number, timestamp, or receipt details.

## 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-c6fdc1fa/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)