Stablecoin circulating supply broken down by chain, paid per call via x402.
What it does
The `/defi/stablecoin/chains` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It returns stablecoin circulating supply data broken down by blockchain chain. The endpoint requires no query parameters — a simple GET request returns the data. Payment is $0.01 USDC on Base per call via the x402 protocol.
This endpoint is one of 26 DeFi-focused endpoints offered by the same API, which spans token security audits, bridge routing, protocol analytics, gas prices, TVL data, and more. All endpoints use 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 key providing $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`).
The probe captured a sample response snippet showing chain-level data including chain name and total circulating USD (e.g., Ethereum with ~$70 billion peggedUSD). The response schema is not formally specified in the OpenAPI document beyond a generic 200 success, so the exact shape of the full response must be discovered at call time. The endpoint is live, returning a 402 challenge with sample data on unauthenticated requests.
Capabilities
Use cases
- —Monitor stablecoin circulating supply across multiple blockchains
- —Track stablecoin migration between chains over time
- —Feed chain-level stablecoin data into DeFi dashboards or research reports
- —Power automated alerts when stablecoin supply shifts significantly on a chain
- —Provide context for cross-chain bridge or liquidity decisions
Fit
Best for
- —DeFi researchers needing chain-level stablecoin supply snapshots
- —AI agents that need on-demand stablecoin analytics without API key setup
- —Dashboard builders aggregating multi-chain stablecoin data
Not for
- —Historical time-series stablecoin data (this appears to return current snapshots only)
- —Individual stablecoin token-level detail (see /defi/stablecoins for that)
- —Free or high-volume bulk data ingestion (each call costs $0.01)
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get('https://defi.hugen.tokyo/defi/stablecoin/chains')
print(response.json())Example
Response
{
"chains": [
{
"name": "Ethereum",
"totalCirculatingUSD": {
"peggedUSD": 70000000000
}
}
],
"total_chains": 20
}Endpoint
Quality
The endpoint is live with a valid 402 challenge and clear pricing ($0.01 USDC on Base). OpenAPI spec exists but the response schema for this endpoint is unspecified (empty schema). The sample response in the 402 challenge provides partial structure but the full response shape is unknown. Documentation is auto-generated Swagger with no additional prose.
Warnings
- —Response schema is not formally defined in the OpenAPI spec — actual response structure must be discovered empirically.
- —Sample response in the 402 challenge appears truncated (shows only 1 chain out of stated 20).
- —No dedicated pricing page or detailed documentation beyond the Swagger UI.
Citations
- —The API describes itself as '26 DeFi security and data endpoints' with 'one x402 payment per call'https://defi.hugen.tokyo/docs
- —The endpoint is live and returns a 402 challenge indicating $0.01 USDC on Base per callhttps://defi.hugen.tokyo/defi/stablecoin/chains
- —Alternative access via broker, MCP, and x402-pay SDK are documented in the 402 challengehttps://defi.hugen.tokyo/defi/stablecoin/chains
- —Sample response shows chain data with total_chains: 20 and Ethereum at ~$70B peggedUSDhttps://defi.hugen.tokyo/defi/stablecoin/chains