# HALOWERK kettenwerk Token Full Report

> HALOWERK kettenwerk Token Full Report is a paid API for AI agents from kette.halowerk.com, paid per call via x402, $0.014/call, status unknown (last checked 2026-09-14).

Runs identity resolution, verification, authority scanning, and upgrade risk checks on a single ERC-20 token contract and merges them into one consolidated report with per-section attribution.

## Facts

- Endpoint: POST https://kette.halowerk.com/token/report
- Price: $0.014/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-token-full-report-af74e805
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J0oiMrf8gB-1O3WYF4q_T

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-full-report-af74e805 -d '<json body>'
```

Example prompt: Can you run a full token report on 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — full depth, so including upgrade history — and give me the consolidated risk score with any failed checks noted?

## When to prefer this

Use this endpoint when you want a single aggregated risk report on a token without making four separate API calls. It is ideal for agents that need a holistic view of a token's identity, authority, verification status, and upgrade risk in one pass. Prefer individual sub-endpoints only when you need to re-run or drill into a single failed check independently.

## Known failure modes

- Unsupported chain returns validation error
- Invalid token address format (non-0x hex) returns 400
- One or more sub-checks fail — those sections are null and listed in checks_failed, score computed over remaining checks
- RPC unavailability for a chain may cause partial results
- depth=schnell skips upgrade history, reducing coverage
- Payment not received or insufficient USDC results in 402 rejection

## How this service works

Runs the identity resolver, the verification check, the authority scanner and the upgrade risk check against one token and merges them into a single answer. Nothing new is measured here: every statement carries the endpoint number it came from, so any finding can be re-bought individually and checked. A section that fails does not sink the report — it is set to null, listed in checks_failed with its reason, and the score is computed only over the checks that ran, with coverage stated. Sections t

## Output

A merged JSON report combining results from the identity resolver, verification check, authority scanner, and upgrade risk check. Each section carries the originating endpoint number for traceability. Failed sections are set to null and listed in checks_failed with reasons. A composite risk score is computed only over sections that successfully ran, accompanied by a coverage percentage indicating how complete the assessment is.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "arbitrum",
    "optimism",
    "polygon",
    "bsc"
   ],
   "type": "string",
   "description": "Chain the token lives on."
  },
  "depth": {
   "enum": [
    "schnell",
    "voll"
   ],
   "type": "string",
   "default": "voll",
   "description": "\"schnell\" skips the upgrade history, which needs a log scan; \"voll\" runs everything available."
  },
  "token": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Token contract address."
  }
 }
}
```

## More

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