# HALOWERK kettenwerk Token Authority Scanner

> HALOWERK kettenwerk Token Authority Scanner is a paid API for AI agents from kette.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-13).

Scans a token contract's runtime bytecode for dangerous privileged functions and tests whether they are actually restricted, reporting each finding with its four-byte selector

## Facts

- Endpoint: POST https://kette.halowerk.com/token/authorities?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-kettenwerk-token-authority-scanner-51454de2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZW7PwUWpAdUS8dKt_aPJd

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-scanner-51454de2 -d '<json body>'
```

Example prompt: Can you scan the token at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum and check whether its dangerous admin functions are actually restricted or callable by anyone — I want to see the four-byte selectors for every risky function found?

## When to prefer this

Use this endpoint when you need cryptographic, bytecode-level evidence of dangerous functions rather than relying on project documentation or whitepapers. It is preferred over generic contract explorers when you need the four-byte selector as proof, when you want to confirm ownership renouncement by the zero address rather than trust a claim, and when you need to know whether a dangerous function is actually callable from a neutral address via simulation. Ideal for pre-investment due diligence, token listing review, or DeFi security monitoring pipelines.

## Known failure modes

- Contract address does not exist on the specified chain — returns an error indicating no bytecode found
- Chain enum value not supported — returns validation error
- Token address fails the 0x hex pattern check — returns schema validation error
- Contract is a proxy and inner implementation bytecode is not accessible — may miss delegated dangerous functions
- RPC timeout or node unreachability on the specified chain — returns upstream error
- Token has no owner() function — renouncement check may be inconclusive

## How this service works

Reads the contract itself rather than a project's claims. Ownership renouncement is checked, not believed: the zero address in owner() is evidence, a sentence in a whitepaper is not. Dangerous functions are found by their four-byte selectors in the runtime bytecode, and every finding names the function and the selector — a selector that is merely absent from the dispatch table is not reported. Whether a function is actually restricted is then tested by simulating the call from a neutral address 

## Output

A list of detected dangerous or privileged functions found in the contract's runtime bytecode, each identified by its human-readable function name and its four-byte selector. For each finding, the result indicates whether the function is actually access-restricted when called from a neutral address (simulated, read-only). Ownership renouncement is confirmed by inspecting the owner() return value for the zero address, not by any off-chain claim.

## 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-scanner-51454de2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kette.halowerk.com](https://www.zero.xyz/host/kette.halowerk.com/llms.txt)