Solana token security audit via x402 — honeypot, tax, holder, and DEX checks for $0.01/call.
What it does
This endpoint performs a security audit on any Solana token by address. It is part of the DeFi Intelligence API hosted at defi.hugen.tokyo, which offers 26 DeFi security and data endpoints accessible via the x402 payment protocol. A single GET request with a Solana token address returns security signals including whether the token is open-source, mintable, a honeypot, its buy/sell tax rates, holder count, DEX listing status, and trust-list membership. Payment is $0.01 USDC on Base per call.
The endpoint requires one query parameter: `address` (the Solana token mint address). No API keys or rate limits are documented. Alternative access methods are available: a broker API (POST to discovery.hugen.tokyo/broker/call with an API key), an MCP server at mcp.hugen.tokyo, or the `x402-pay` Python SDK for wallet-free one-line access.
The broader DeFi Intelligence API also covers EVM token security, address security, NFT audits, rug-pull detection, phishing URL checks, transaction simulation, approval security, malicious address checks, dApp audits, bridge quoting/routing/status, gas prices, protocol info/TVL/fees, token prices, stablecoin data, and DEX volume. All endpoints follow the same x402 pay-per-call model.
Capabilities
Use cases
- —Check if a Solana token is a honeypot before buying
- —Verify buy/sell tax rates on a Solana token
- —Assess holder distribution and DEX listing status for a Solana token
- —Automate Solana token due diligence in a trading bot
- —Screen new Solana meme coins for security red flags
Fit
Best for
- —AI agents that need on-demand Solana token security data
- —Trading bots performing pre-trade safety checks on Solana tokens
- —DeFi dashboards displaying token risk scores
- —Developers who want a single API call without managing upstream service keys
Not for
- —EVM-chain token audits (use /defi/token instead)
- —Historical token security data or time-series analysis
- —Real-time on-chain transaction monitoring or streaming
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
result = x402_pay.get(
'https://defi.hugen.tokyo/defi/token/solana?address=So11111111111111111111111111111111111111112'
)
print(result)Example
Request
{
"url": "https://defi.hugen.tokyo/defi/token/solana?address=So11111111111111111111111111111111111111112",
"method": "GET"
}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 sample response data), has a full OpenAPI spec with parameter definitions, and pricing is clearly stated at $0.01 USDC on Base. However, the response schema is untyped (empty schema object in OpenAPI), and no detailed field-level documentation exists. The sample response in the 402 challenge provides the only insight into the response shape.
Warnings
- —Response schema is not formally defined in the OpenAPI spec — the sample in the 402 challenge is the only documentation of response fields.
- —Root URL returns 404; no dedicated landing page or detailed docs beyond the auto-generated Swagger UI at /docs.
- —No rate limit or SLA information is documented.
Citations
- —The endpoint is part of a 26-endpoint DeFi Intelligence API with x402 pay-per-call at $0.01 USDC on Base.https://defi.hugen.tokyo/docs
- —The /defi/token/solana endpoint accepts a required 'address' query parameter described as 'Solana token address'.https://defi.hugen.tokyo/openapi.json
- —Alternative access via broker, MCP, and x402-pay SDK is available.https://defi.hugen.tokyo/defi/token/solana
- —Sample response includes fields: is_open_source, is_proxy, is_mintable, is_honeypot, buy_tax, sell_tax, holder_count, is_in_dex, trust_list.https://defi.hugen.tokyo/defi/token/solana