# HALOWERK kettenwerk — Token Authority Inspector

> HALOWERK kettenwerk — Token Authority Inspector 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-15).

Analyzes a smart contract token's privileged authority addresses (owners, admins, minters, pausers, etc.) across major EVM chains, optionally simulating calls to dangerous functions to verify access control.

## Facts

- Endpoint: POST https://kette.netzhandwerker.de/token/authorities
- Price: $0.005/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-authority-inspector-a74e660f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TEM7rHV0rCUMRqsupEtuq

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-authority-inspector-a74e660f -d '<json body>'
```

Example prompt: Check the authority addresses on this Ethereum token contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 — simulate the dangerous function calls too so we can see if access is actually restricted.

## When to prefer this

Use this endpoint when you need to quickly surface centralization and rug-pull risks in an EVM token contract without running a full audit. It is especially valuable for pre-investment due diligence, exchange listing checks, or DeFi protocol risk scoring, where you need to know who can mint, pause, freeze, or upgrade a token. Prefer this over generic block explorers when you want structured authority data and active access-control simulation rather than raw ABI browsing.

## Known failure modes

- Invalid or non-checksummed contract address returns a validation error
- Contract address exists but is not a token contract — may return empty or partial results
- Unsupported chain value returns an enum validation error
- Contract has no recognizable authority functions — returns empty authority list
- RPC or on-chain read failure for the specified chain may cause partial results or timeout
- probe_calls simulation may be inconclusive if contract uses non-standard access patterns

## How this service works

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

## Output

Returns a structured breakdown of all privileged authority addresses found in the token contract (e.g. owner, admin, minter, pauser, blacklister), their roles, and — if probe_calls is enabled — the results of read-only simulated calls to potentially dangerous functions showing whether access is restricted or open.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "arbitrum",
    "optimism",
    "polygon",
    "bsc"
   ],
   "type": "string",
   "description": "Chain the token lives on."
  },
  "token": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Token contract address."
  },
  "probe_calls": {
   "type": "boolean",
   "default": true,
   "description": "Simulate each dangerous function from a neutral address to test whether access is restricted. Read-only, nothing is sent."
  }
 }
}
```

## More

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