Token security audit via x402 — check honeypots, taxes, rug-pull flags for EVM tokens.
What it does
The `/defi/token` endpoint on the DeFi Intelligence API returns security and risk data for EVM-based tokens. Given a chain ID (e.g., 1 for Ethereum, 56 for BSC, 8453 for Base) and a token contract address, it reports whether the token is open-source, mintable, a honeypot, listed on a DEX, on a trust list, along with buy/sell tax rates and holder count. Payment is $0.01 USDC on Base per call via the x402 protocol — no API key or account setup required.
This endpoint is part of a larger DeFi Intelligence API suite hosted at defi.hugen.tokyo that exposes 26 paid endpoints covering token audits, address security, NFT security, rug-pull detection, phishing checks, bridge routing, gas prices, protocol analytics (TVL, fees), token prices, stablecoin data, and DEX volume. All endpoints use the same x402 payment model. Alternative access methods include a broker API (with a free API key and $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`pip install x402-pay`).
The response schema is not formally documented beyond the sample embedded in the 402 challenge, but the sample shows fields like `is_open_source`, `is_proxy`, `is_mintable`, `is_honeypot`, `buy_tax`, `sell_tax`, `holder_count`, `is_in_dex`, and `trust_list`. The endpoint accepts GET requests with required query parameters `chain` (chain ID string) and `address` (token contract address string). A Solana-specific variant exists at `/defi/token/solana`.
Capabilities
Use cases
- —Screening a token contract for honeypot or rug-pull indicators before trading
- —Checking buy and sell tax rates on a token to estimate slippage
- —Verifying whether a token is on a trust list and listed on a DEX
- —Automated agent workflows that need per-call token security data without API key management
- —Building a DeFi dashboard that surfaces token risk scores across multiple EVM chains
Fit
Best for
- —AI agents needing pay-per-call token security data with no signup
- —Developers building multi-chain DeFi safety tools
- —Traders who want quick programmatic honeypot and tax checks
Not for
- —Solana tokens (use the /defi/token/solana sibling endpoint instead)
- —Deep smart-contract source-code auditing or formal verification
- —Free or high-volume bulk token scanning (every call costs $0.01)
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
resp = x402_pay.get(
'https://defi.hugen.tokyo/defi/token?chain=1&address=0xdac17f958d2ee523a2206206994597c13d831ec7'
)
print(resp.json())Example
Request
{
"url": "https://defi.hugen.tokyo/defi/token?chain=1&address=0xdac17f958d2ee523a2206206994597c13d831ec7",
"method": "GET",
"headers": {
"Accept": "application/json"
}
}Response
{
"buy_tax": "0",
"is_proxy": false,
"sell_tax": "0.03",
"is_in_dex": true,
"trust_list": true,
"is_honeypot": false,
"is_mintable": false,
"holder_count": "15234",
"is_open_source": true
}Endpoint
Quality
The endpoint is live (402 challenge captured with a sample response), and a full OpenAPI spec is available listing parameters. However, the response schema is not formally defined (empty schema in OpenAPI), and the sample response is embedded only in the 402 challenge. No dedicated documentation page or detailed field descriptions exist beyond the Swagger UI.
Warnings
- —Response schema is not formally specified in the OpenAPI document — the sample is inferred from the 402 challenge payload only.
- —Root URL returns 404; no dedicated landing page or documentation beyond the auto-generated /docs Swagger UI.
- —Upstream data sources aggregated by this API are not disclosed.
Citations
- —The endpoint costs $0.01 USDC on Base per call via x402https://defi.hugen.tokyo/defi/token
- —The API has 26 DeFi security and data endpointshttps://defi.hugen.tokyo/docs
- —Alternative access via broker API key with $0.05 free credithttps://defi.hugen.tokyo/defi/token
- —MCP server available at mcp.hugen.tokyohttps://defi.hugen.tokyo/defi/token
- —Python SDK available as x402-payhttps://defi.hugen.tokyo/defi/token
- —Required parameters are chain (chain ID) and address (token contract address)https://defi.hugen.tokyo/openapi.json