# HALOWERK kettenwerk Wallet Activity

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

Retrieves recent on-chain transaction activity for a given wallet address across multiple EVM-compatible chains within a specified time window.

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/wallet/activity
- Price: $0.005/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-activity-bf3c75fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uTGr5XYMmvzs06wmlF9ud

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

Example prompt: Can you pull up the last 30 days of on-chain activity for wallet 0xAbCd1234...5678 across Ethereum, Base, Arbitrum, and Optimism — up to 150 transactions per chain?

## When to prefer this

Choose this endpoint when you need multi-chain EVM wallet transaction history aggregated in a single call, particularly across Ethereum, Base, Arbitrum, and Optimism. It is well-suited for agents that need to audit, monitor, or summarize on-chain activity for a known wallet address without setting up direct RPC connections to each chain. Prefer it over generic blockchain explorers when you want a paid, structured, aggregated response via the x402 micropayment protocol.

## Known failure modes

- Invalid wallet address format (not 0x followed by 40 hex chars) returns validation error
- Unsupported or misspelled chain names result in empty or error responses
- Limit outside the 10–200 range is rejected
- Payment failure via x402 (insufficient USDC balance) blocks the request
- Wallet with no transactions in the time window returns empty results
- Rate limiting or upstream chain RPC unavailability may cause timeouts

## How this service works

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

## Output

Returns a structured list of on-chain transactions for the specified wallet across the requested EVM chains within the given time window, including transaction details such as timestamps, amounts, chain identifiers, and counterparties, bounded by the configured per-chain transaction limit.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "default": 100,
   "maximum": 200,
   "minimum": 10,
   "description": "Upper bound of transactions examined per chain."
  },
  "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",
   "description": "Time window. Default 30d."
  }
 }
}
```

## More

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