Rug-pull detection for EVM tokens via x402 micropayment — $0.01 per call.
What it does
The `/defi/rugpull` endpoint on the DeFi Intelligence API at defi.hugen.tokyo checks whether a token contract on a given EVM chain exhibits rug-pull characteristics. It accepts two required query parameters: `chain` (a numeric chain ID such as 1 for Ethereum, 56 for BSC, or 8453 for Base) and `address` (the token contract address). The endpoint is part of a larger suite of 26 DeFi security and data endpoints covering token audits, address screening, NFT security, phishing detection, bridge routing, protocol analytics, and more.
Payment is handled via the x402 protocol: each call costs $0.01 USDC on Base. No API key or account registration is required for direct x402 usage — callers simply satisfy the 402 payment challenge. Alternative access methods are also advertised: a broker API key (free key with $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`pip install x402-pay`). The API is described as open-source and not a proxy.
The endpoint returned a valid 402 challenge during probing, confirming it is live. A full OpenAPI 3.1 spec is available, though response schemas for this specific endpoint are empty (no documented response shape). No rate limits are documented.
Capabilities
Use cases
- —Screening a newly discovered token for rug-pull risk before buying
- —Automated portfolio monitoring that flags tokens exhibiting rug-pull patterns
- —Building a DeFi security dashboard that aggregates multiple risk signals
- —Agent-driven trading bots that gate token purchases on safety checks
- —Wallet or dApp front-ends that warn users about risky tokens
Fit
Best for
- —AI agents that need per-call DeFi security checks without API key setup
- —Developers building token screening tools across multiple EVM chains
- —Automated trading systems that require low-cost, on-demand rug-pull analysis
Not for
- —Solana-only token analysis (use the separate /defi/token/solana endpoint)
- —Comprehensive smart-contract source-code auditing
- —High-volume batch scanning where per-call micropayments become impractical
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
resp = x402_pay.get(
'https://defi.hugen.tokyo/defi/rugpull?chain=1&address=0xdac17f958d2ee523a2206206994597c13d831ec7'
)
print(resp.json())Example
Request
{
"url": "https://defi.hugen.tokyo/defi/rugpull?chain=1&address=0xdac17f958d2ee523a2206206994597c13d831ec7",
"method": "GET"
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and has a full OpenAPI spec with clear input parameters. However, the response schema is empty — there is no documentation of what the rugpull detection response actually contains. No example responses, no field descriptions for output. Pricing is clear at $0.01 USDC on Base.
Warnings
- —Response schema is not documented — the OpenAPI spec has an empty schema object for the 200 response, so the shape of the rug-pull detection result is unknown.
- —No example responses are provided anywhere in the crawled material.
- —Root URL returns 404; documentation is only available at /docs.
- —owner_address is the zero address (0x000...000), which may indicate a placeholder or test configuration.
Citations
- —The endpoint costs $0.01 USDC on Base per callhttps://defi.hugen.tokyo/defi/rugpull
- —26 DeFi security and data endpoints — token audits, bridge routing, protocol analyticshttps://defi.hugen.tokyo/docs
- —The API is described as open-source and not a proxyhttps://defi.hugen.tokyo/defi/rugpull
- —Alternative access via broker, MCP, and x402-pay SDKhttps://defi.hugen.tokyo/defi/rugpull
- —Required parameters are chain (Chain ID) and address (Token contract address)https://defi.hugen.tokyo/openapi.json