# HALOWERK kettenwerk Token Honeypot Detector

> HALOWERK kettenwerk Token Honeypot Detector 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-15).

Simulates a transfer on an ERC-20 token to detect honeypot traps and trading restrictions on EVM-compatible chains.

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/token/honeypot
- Price: $0.01/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-token-honeypot-detector-64ea4b1b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_24Ti5KMnBRAOc7Ji6Uxkf

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-token-honeypot-detector-64ea4b1b -d '<json body>'
```

Example prompt: Can you check if the token at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum is a honeypot — use holder address 0xF977814e90dA44bFA03b6295A0616a897441aceE for the simulation so the result is meaningful?

## When to prefer this

Use this endpoint when you need to programmatically check whether an ERC-20 token is a honeypot before trading, investing, or integrating it — especially on chains like Ethereum, Base, Arbitrum, Optimism, Polygon, or BSC. It is particularly valuable for DeFi bots, portfolio auditors, or any agent workflow that needs to validate token safety at low cost ($0.01 USDC per call). Prefer this over manual contract inspection when speed and automation matter.

## Known failure modes

- Invalid or non-existent contract address returns an error or inconclusive result
- Unsupported chain identifier causes a bad request error
- No holder address provided may yield a less reliable simulation result
- Contract with no on-chain liquidity may produce ambiguous results
- RPC node unavailability for the target chain may cause timeout or failure

## How this service works

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

## Output

The endpoint returns the result of a simulated ERC-20 transfer, indicating whether the token exhibits honeypot behavior (i.e., whether sells/transfers are blocked or penalized), along with any detected trading restrictions. Providing a real holder address significantly improves result accuracy.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain identifier, for example ethereum, base, arbitrum, optimism, polygon or bsc."
  },
  "token": {
   "type": "string",
   "description": "ERC-20 contract address, 0x followed by 40 hex characters."
  },
  "holder": {
   "type": "string",
   "description": "Optional: an address that actually holds the token. Its balance is used as the source for the transfer simulation, which makes the result far more meaningful."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-kettenwerk-token-honeypot-detector-64ea4b1b/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)