List all DeFi protocols with TVL and category data via a single x402-paid API call.
What it does
The `/defi/protocols` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It returns a list of all tracked DeFi protocols, including their names, TVL (Total Value Locked), and category classifications (e.g., Liquid Staking, Lending). The endpoint requires no query parameters — a simple GET request returns the full protocol list. Payment is handled via the x402 protocol at $0.01 USDC per call on Base.
This endpoint is one of 26 DeFi-focused endpoints offered by the same API, which spans token security audits, rugpull detection, bridge routing, gas prices, stablecoin analytics, DEX volume, and more. All endpoints follow the same x402 pay-per-call model with no API keys or rate limits required. Alternative access methods include a broker API (with a free API key providing $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`).
The OpenAPI spec (v3.1.0) documents the endpoint but does not include a response schema for `/defi/protocols`. The x402 challenge includes a sample response showing protocol objects with `name`, `tvl`, and `category` fields. The endpoint returned a valid 402 challenge when probed, confirming it is live.
Capabilities
Use cases
- —Retrieve a snapshot of all tracked DeFi protocols with their TVL for portfolio dashboards
- —Compare protocol categories and TVL rankings programmatically
- —Feed protocol metadata into an AI agent for DeFi research or risk analysis
- —Build leaderboards or analytics views of the DeFi ecosystem
- —Monitor DeFi protocol landscape changes over time
Fit
Best for
- —AI agents needing structured DeFi protocol data without API key setup
- —Developers building DeFi dashboards who want pay-per-call pricing
- —Quick one-off lookups of protocol TVL and categories
Not for
- —High-frequency polling where per-call costs would accumulate quickly
- —Historical TVL time-series data (use /defi/tvl for per-protocol history instead)
- —Non-crypto use cases
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get('https://defi.hugen.tokyo/defi/protocols')
print(response.json())Example
Response
{
"total": 5000,
"protocols": [
{
"tvl": 15000000000,
"name": "Lido",
"category": "Liquid Staking"
},
{
"tvl": 12500000000,
"name": "Aave",
"category": "Lending"
}
]
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and has an OpenAPI spec, but the response schema for /defi/protocols is empty. The sample response in the x402 challenge provides some structure but is only illustrative. No dedicated docs page or pricing page exists beyond the OpenAPI listing.
Warnings
- —Response schema is not defined in the OpenAPI spec — the sample in the 402 challenge is the only indication of response structure.
- —No dedicated documentation or pricing page found (root, /pricing, /api, /README all return 404).
- —Sample response fields (total, protocols array with name/tvl/category) are inferred from the x402 challenge and may not represent the full response shape.
Citations
- —The API offers 26 DeFi security and data endpoints with x402 pay-per-call pricing.https://defi.hugen.tokyo/docs
- —The /defi/protocols endpoint is a GET with no required parameters.https://defi.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call, with broker, MCP, and SDK alternatives available.https://defi.hugen.tokyo/defi/protocols
- —Sample response includes protocol objects with name, tvl, and category fields.https://defi.hugen.tokyo/defi/protocols