# HALOWERK kettenwerk Wallet Counterparties

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

Returns a graph of wallet counterparties (addresses that have interacted with a given wallet) across multiple EVM chains within a configurable time window and depth.

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/wallet/counterparties
- Price: $0.01/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-wallet-counterparties-bbaf30a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CLm36_u0q0Th4UDo7VbtR

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-wallet-counterparties-bbaf30a7 -d '<json body>'
```

Example prompt: Can you pull the counterparty graph for wallet 0xAbCd1234...5678 across Ethereum, Base, and Arbitrum for the last 30 days, keeping only addresses with at least 2 interactions?

## When to prefer this

Choose this endpoint when you need to discover on-chain counterparty relationships for a specific EVM wallet across Ethereum, Base, Arbitrum, and/or Optimism, especially when you want configurable graph depth (1 or 2 hops), time-windowed analysis, and minimum-interaction filtering. Prefer it over generic block explorers when you need structured graph data rather than raw transaction lists.

## Known failure modes

- Invalid wallet address format (not 0x + 40 hex chars) returns a validation error
- Unsupported chain names in the chains array may be ignored or return an error
- depth > 2 is rejected by design
- Wallet with no on-chain activity returns an empty graph
- Rate limiting or payment failure (x402) blocks the request

## How this service works

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

## Output

A graph structure describing on-chain counterparties: wallet addresses that have interacted with the queried wallet, along with edge metadata (interaction counts, chains), filtered by the specified depth, time window, chains, and minimum interaction threshold.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "depth": {
   "type": "integer",
   "default": 1,
   "maximum": 2,
   "minimum": 1,
   "description": "Graph depth. Two is the hard maximum by design."
  },
  "chains": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 4,
   "description": "Chains to query. Default: ethereum, base, arbitrum, optimism."
  },
  "wallet": {
   "type": "string",
   "description": "Wallet address, 0x followed by 40 hex characters."
  },
  "window": {
   "enum": [
    "7d",
    "30d",
    "90d",
    "all"
   ],
   "type": "string",
   "default": "30d"
  },
  "min_interactions": {
   "type": "integer",
   "default": 1,
   "minimum": 1,
   "description": "Only keep edges with at least this many interactions."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-kettenwerk-wallet-counterparties-bbaf30a7/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)