# HALOWERK x402werk — Settlement Transaction Verifier

> HALOWERK x402werk — Settlement Transaction Verifier is a paid API for AI agents from x402.netzhandwerker.de, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Verifies that a blockchain settlement transaction matches expected payment parameters (recipient, token, amount) across multiple EVM chains.

## Facts

- Endpoint: POST https://x402.netzhandwerker.de/settlement/verify
- 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-x402werk-settlement-transaction-verifier-243c7831
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6O6SUNFuMM5Q7QxEAMhiW

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-x402werk-settlement-transaction-verifier-243c7831 -d '<json body>'
```

Example prompt: Can you verify that the Base mainnet transaction 0xabc123...def456 actually sent the correct USDC amount to my wallet address 0xRecipient... — I want to confirm the payment settled as expected before releasing the goods.

## When to prefer this

Use this endpoint when you need to programmatically confirm that an on-chain EVM payment transaction settled correctly against specific expected parameters — particularly in x402-based payment flows where you must validate a settlement tx hash before releasing a resource or continuing a workflow. Prefer this over manual block explorer lookups when automating payment verification across Base, Arbitrum, Ethereum, Polygon, Optimism, Avalanche, or their testnets.

## Known failure modes

- Invalid or malformed tx_hash (not a valid 0x-prefixed 64-char hex) returns validation error
- Unrecognized chain identifier returns error
- Transaction not yet indexed or not found on chain returns not-found error
- Mismatch between expected and actual recipient, asset, or amount returns false match flags rather than an error
- Network or RPC timeout for the specified chain returns a service error
- pay_to address missing (required field) returns a 400-level error

## How this service works

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

## Output

Returns a verification object indicating whether the transaction exists on the specified chain, and boolean match flags for whether the recipient address (pay_to), token asset, and transferred amount align with the expected values provided in the request. If optional fields like asset or amount_units are omitted, the corresponding match fields are returned as null.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "arb",
    "arbitrum",
    "arbitrum-one",
    "avalanche",
    "avax",
    "base",
    "base-mainnet",
    "base-sepolia",
    "basesepolia",
    "eip155:1",
    "eip155:10",
    "eip155:137",
    "eip155:42161",
    "eip155:43114",
    "eip155:8453",
    "eip155:84532",
    "eth",
    "ethereum",
    "ethereum-mainnet",
    "mainnet",
    "matic",
    "op",
    "op-mainnet",
    "optimism",
    "polygon"
   ],
   "type": "string",
   "description": "Chain of the transaction, as CAIP-2 (\"eip155:8453\"), as a short name (\"base\") or as the chain id (\"8453\")."
  },
  "tx_hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Hash of the settlement transaction."
  },
  "expected": {
   "type": "object",
   "required": [
    "pay_to"
   ],
   "properties": {
    "asset": {
     "type": "string",
     "description": "Expected token contract address, or \"native\" for the chain coin. Omit to accept any token; asset_matches is then null."
    },
    "pay_to": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$",
     "description": "Address that was supposed to receive the payment — the seller, not the token contract."
    },
    "amount_units": {
     "type": "string",
     "pattern": "^[0-9]{1,78}$",
     "description": "Expected amount as an integer in the smallest unit of the token. Omit to skip the amount comparison; amount_matches is then null."
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-x402werk-settlement-transaction-verifier-243c7831/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.netzhandwerker.de](https://www.zero.xyz/host/x402.netzhandwerker.de/llms.txt)