# HALOWERK kettenwerk — ERC-20 Token Transfer Restrictions Lookup

> HALOWERK kettenwerk — ERC-20 Token Transfer Restrictions Lookup is a paid API for AI agents from kette.netzhandwerker.de, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-13).

Retrieves transfer restriction rules (e.g. lockups, blacklists, whitelist requirements) for a given ERC-20 token on a specified blockchain network

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/token/restrictions
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-kettenwerk-erc-20-token-transfer-restrictions-lookup-335911fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BNJ7xnqnY3VdAloyJsMl6

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-erc-20-token-transfer-restrictions-lookup-335911fb -d '<json body>'
```

Example prompt: Can you check the transfer restrictions for the ERC-20 token at address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — I want to know if there are any lockups, blacklists, or whitelist requirements before I try to move it.

## When to prefer this

Use this endpoint when you need onchain-sourced, structured data about ERC-20 transfer restrictions for a specific contract — especially for compliance checks, pre-transfer validation, token security audits, or DeFi integrations across Ethereum, Base, Arbitrum, Optimism, Polygon, and BSC. Prefer it over generic block explorers when you need machine-readable restriction metadata rather than human-readable UI output.

## Known failure modes

- Invalid or non-checksummed ERC-20 contract address returns a validation error
- Unsupported chain identifier returns an error indicating the chain is not available
- Contract address exists but has no restriction module — may return empty or null restrictions
- Network connectivity issues or RPC failures may result in a timeout or 5xx error
- Payment failure via x402 (insufficient USDC on Base Mainnet) blocks the request entirely

## How this service works

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

## Output

Returns structured data describing the transfer restriction rules attached to the specified ERC-20 contract on the given chain, which may include restriction types such as blacklists, whitelists, transfer caps, lockup periods, or compliance flags indicating whether token movements are subject to programmatic controls.

## 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."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-kettenwerk-erc-20-token-transfer-restrictions-lookup-335911fb/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)