Check URLs for phishing via x402 micropayment — part of a 26-endpoint DeFi security API.
What it does
The `/defi/phishing` endpoint on the DeFi Intelligence API checks whether a given URL is a known phishing site. It is one of 26 DeFi-focused security and data endpoints hosted at defi.hugen.tokyo, all gated by the x402 payment protocol at $0.01 USDC per call on Base. The endpoint accepts a single required query parameter (`url`) and returns a phishing assessment.
The broader API suite covers token security audits (EVM and Solana), address and NFT security checks, rug-pull detection, dApp audits, approval security, malicious-address lookups, EVM transaction simulation, cross-chain bridge quoting/routing/status, gas prices, protocol analytics (TVL, fees, info), token prices, stablecoin data, and DEX volume. No API keys or rate limits are required — payment is handled per-call via x402. Alternative access methods include a broker API (with a free $0.05 credit key), an MCP server at mcp.hugen.tokyo with 58 tools, and a Python SDK (`x402-pay`).
The endpoint returned a valid 402 challenge when probed, confirming it is live. The OpenAPI 3.1 spec is published at `/openapi.json` and interactive docs are available at `/docs`. Response schemas for individual endpoints are not detailed in the spec (empty schema objects), so the exact shape of the phishing-check response is not documented.
Capabilities
Use cases
- —Screening URLs before a user clicks links in DeFi chat channels or forums
- —Automated phishing detection in wallet browser extensions
- —Pre-flight URL validation in trading bots before interacting with dApps
- —Security dashboards that flag suspicious domains in real time
- —Agent workflows that verify site legitimacy before submitting transactions
Fit
Best for
- —AI agents needing per-call phishing checks without API key setup
- —DeFi security tooling that aggregates multiple upstream threat feeds
- —Developers who want a single x402 payment per query with no subscription
Not for
- —Bulk scanning of millions of URLs (per-call payment model would be costly)
- —General non-crypto phishing detection where specialized email/web filters are more appropriate
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
resp = x402_pay.get(
'https://defi.hugen.tokyo/defi/phishing?url=https://example-scam.com'
)
print(resp.json())Example
Request
{
"url": "https://defi.hugen.tokyo/defi/phishing?url=https://example-scam.com",
"method": "GET"
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and has a published OpenAPI 3.1 spec with clear parameter definitions. However, response schemas for the phishing endpoint are empty, no example responses are provided, and there is no dedicated documentation page beyond the auto-generated Swagger UI. Pricing is clear ($0.01 USDC on Base).
Warnings
- —Response schema for /defi/phishing is not defined in the OpenAPI spec (empty schema object) — actual response shape is unknown.
- —No example responses or detailed field documentation available for this endpoint.
- —Root URL returns 404; documentation is only at /docs.
Citations
- —The /defi/phishing endpoint accepts a required 'url' query parameter and is described as 'Phishing Check' in the OpenAPI spec.https://defi.hugen.tokyo/openapi.json
- —The API has 26 DeFi security and data endpoints with one x402 payment per call.https://defi.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call, as stated in the 402 challenge.https://defi.hugen.tokyo/defi/phishing
- —Alternative access via broker API, MCP server, and x402-pay Python SDK is available.https://defi.hugen.tokyo/defi/phishing