# defi.hugen.tokyo Token Security Audit

> defi.hugen.tokyo Token Security Audit is a paid API for AI agents from defi.hugen.tokyo, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Audits any EVM token contract for honeypot traps, hidden taxes, proxy upgradability, mintable supply, blacklists, and holder concentration risks across 20+ chains

## Facts

- Endpoint: GET https://defi.hugen.tokyo/defi/token
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-hugen-tokyo-8b63e282
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P3_Ctu6b0K__zNY7OijLH

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 defi-hugen-tokyo-8b63e282
```

Example prompt: Can you run a security audit on this token contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — I want to know if it's a honeypot, has hidden buy/sell taxes, blacklist functions, or any mintable supply risks?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically assess token safety before a swap, investment recommendation, or portfolio action on any EVM-compatible chain. It is preferable over generic block explorers because it aggregates multiple risk signals (honeypot, tax, proxy, mintability, blacklist, concentration) into a single structured response without requiring manual contract inspection or multiple API keys.

## Known failure modes

- Invalid or unrecognized contract address returns an error or empty result
- Unsupported chain identifier causes a failed lookup
- Newly deployed contracts with minimal on-chain data may return incomplete analysis
- Network congestion on the target chain may delay response
- Payment failure (insufficient USDC balance) returns a 402 error

## How this service works

Token security audit on any EVM chain — detect honeypots, hidden buy/sell taxes, proxy contracts, mintable supply, blacklist functions, and holder concentration risks. Covers Ethereum, BSC, Polygon, Arbitrum, Base, and 20+ chains. No API keys or rate limit management needed. Accepts USDC payments on Base and Solana

## Output

Returns a structured security report for the token contract including: honeypot verdict, detected buy and sell tax percentages, whether the contract uses a proxy/upgradeable pattern, whether the owner can mint new supply, presence of blacklist or transfer-restriction functions, and holder concentration data — all derived from on-chain analysis of the contract bytecode and state.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-hugen-tokyo-8b63e282/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from defi.hugen.tokyo](https://www.zero.xyz/host/defi.hugen.tokyo/llms.txt)