Check wallet/contract address security via x402-paid DeFi Intelligence API
What it does
The `/defi/address` endpoint on the DeFi Intelligence API checks whether a given wallet or contract address is associated with malicious activity, scams, or other security risks. It is one of 26 DeFi-focused endpoints hosted at defi.hugen.tokyo, all payable per-call via the x402 protocol at $0.01 USDC on Base. No API keys or rate limits are required — payment is handled inline with each request.
The endpoint accepts a single required query parameter `address` (the wallet or contract address to check) and returns a JSON response. The x402 challenge confirms the endpoint is live and indicates the address is evaluated for malicious activity (the sample challenge includes fields like `is_malicious_address` and `contract_address`). The broader API suite covers token audits, NFT security, rug-pull detection, phishing checks, bridge routing, protocol analytics (TVL, fees, DEX volume), gas prices, and transaction simulation across multiple EVM chains and Solana.
Alternative access methods are available: a broker API at discovery.hugen.tokyo (use an API key, no wallet needed), an MCP server at mcp.hugen.tokyo, and a Python SDK (`pip install x402-pay`). The OpenAPI 3.1 spec is published at `/openapi.json` and interactive docs are at `/docs`. Response schemas for individual endpoints are not detailed in the spec beyond validation errors.
Capabilities
Use cases
- —Screen a wallet address for known malicious activity before interacting with it
- —Automate address security checks in a DeFi trading bot or portfolio manager
- —Verify counterparty addresses in peer-to-peer crypto transactions
- —Integrate address risk assessment into a compliance or AML workflow
- —Agent-driven due diligence on contract addresses before token approvals
Fit
Best for
- —AI agents needing on-demand address security checks with no setup
- —DeFi applications that want per-call pricing without API key management
- —Developers building security tooling across multiple EVM chains
Not for
- —Bulk screening of millions of addresses (per-call pricing adds up)
- —Users who need detailed forensic chain analysis or transaction tracing
- —Applications that cannot settle USDC payments on Base
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
resp = x402_pay.get(
'https://defi.hugen.tokyo/defi/address?address=0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18'
)
print(resp.json())Example
Request
{
"url": "https://defi.hugen.tokyo/defi/address?address=0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18",
"method": "GET"
}Response
{
"contract_address": false,
"is_malicious_address": false
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a published OpenAPI 3.1 spec and interactive docs. However, the response schema for /defi/address is empty in the spec, and no example responses are documented. The example response is inferred from the x402 challenge sample fields, which may not represent the full output.
Warnings
- —Response schema for /defi/address is not defined in the OpenAPI spec (empty schema object)
- —Example response is inferred from x402 challenge fields and may be incomplete
- —No dedicated pricing page found; price ($0.01 USDC on Base) is only stated in the 402 challenge
- —Root URL returns 404; documentation only available at /docs
Citations
- —The endpoint requires a single query parameter 'address' described as 'Wallet or contract address to check'https://defi.hugen.tokyo/docs
- —The API has 26 DeFi security and data endpoints with one x402 payment per callhttps://defi.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per callhttps://defi.hugen.tokyo/defi/address
- —Alternative access via broker, MCP, and Python SDK (x402-pay) is availablehttps://defi.hugen.tokyo/defi/address
- —The x402 challenge sample includes is_malicious_address and contract_address fieldshttps://defi.hugen.tokyo/defi/address