{"ok":true,"host":"defi.hugen.tokyo","status":"ready","manifest":{"positioning":"This host serves agents and developers that need to enumerate, validate, or research DeFi infrastructure before taking action elsewhere. It covers four distinct domains: supported blockchain networks, stablecoin supply and peg data, DeFi protocol metadata, and cross-chain bridge capabilities. It is a discovery and research layer, not an execution layer — agents must route to dedicated swap or bridge execution APIs to act on what they find here.","host_overview":"defi.hugen.tokyo provides read-only metadata and analytics endpoints for DeFi infrastructure, including protocol discovery, stablecoin metrics, DEX volume history, and cross-chain bridge capability enumeration. It does not execute trades, fetch live swap quotes, or submit on-chain transactions. All data is sourced from aggregators such as DefiLlama and bridge protocol registries.","routing_guidance":"Use defi.hugen.tokyo when an agent needs to enumerate supported chains, discover DeFi protocols by category or TVL, research stablecoin supply and peg mechanics, identify available bridge protocols and their chain pair coverage, or analyze historical DEX volume for a token. Do not use this host for live swap quotes, real-time token prices, order book data, wallet balance lookups, or executing any on-chain transaction — those require a dedicated DEX aggregator or bridge execution API (e.g., a 1inch, LI.FI, or similar endpoint). Also do not use fetch-bridge-tools or fetch-defi-bridge-chains as substitutes for bridge fee estimation or route optimization; they return static capability metadata only.","capability_clusters":[{"skill_names":["fetch-supported-chains","fetch-defi-bridge-chains"],"cluster_name":"Chain Enumeration","cluster_summary":"Identifies which blockchain networks are available across different DeFi contexts, including general API support and bridge-specific chain metadata with RPC endpoints and relayer flags."},{"skill_names":["fetch-bridge-tools"],"cluster_name":"Bridge Discovery","cluster_summary":"Enumerates available cross-chain bridge protocols and the specific source-to-destination chain pairs each supports, enabling route planning before requesting quotes or executing transfers."},{"skill_names":["fetch-defi-protocols","fetch-dex-volume"],"cluster_name":"Protocol and Market Intelligence","cluster_summary":"Provides DeFi protocol records with TVL, categories, and chain coverage, plus historical DEX trading volume time series for specific tokens, supporting research and liquidity analysis."},{"skill_names":["fetch-stablecoin-metrics"],"cluster_name":"Stablecoin Analytics","cluster_summary":"Returns aggregated circulating supply, peg type, peg mechanism, and per-chain distribution data for major stablecoins, useful for monitoring peg health and cross-chain supply allocation."}],"cross_skill_workflows":[{"steps":[{"skill_name":"fetch-defi-bridge-chains","description":"Enumerate all bridge-supported chains and resolve their IDs, RPC endpoints, and relayer support flags to validate the intended source and destination chains."},{"skill_name":"fetch-bridge-tools","description":"Retrieve available bridge protocols and their supported fromChainId/toChainId pairs to identify which bridges can service the validated chain pair."}],"when_to_use":"Use when an agent needs to plan a cross-chain token transfer by first confirming both the source and destination chains are supported, then identifying which bridge protocols cover that chain pair.","workflow_name":"Cross-Chain Bridge Route Planning"},{"steps":[{"skill_name":"fetch-supported-chains","description":"Retrieve the full list of supported chain names and IDs to validate or resolve the target chain identifier."},{"skill_name":"fetch-defi-protocols","description":"Fetch DeFi protocol records and filter by the validated chain to identify relevant protocols, their categories, TVL, and associated URLs."}],"when_to_use":"Use when an agent needs to discover DeFi protocols available on a specific chain and must first confirm the chain ID is recognized by the API.","workflow_name":"DeFi Protocol Research with Chain Validation"},{"steps":[{"skill_name":"fetch-supported-chains","description":"Confirm the target chain name and ID are supported before constructing the volume query."},{"skill_name":"fetch-dex-volume","description":"Fetch historical DEX trading volume time series for the target token address on the validated chain to analyze liquidity and activity trends."}],"when_to_use":"Use when an agent needs to assess trading activity for a token on a specific chain, with chain ID validated before querying volume data.","workflow_name":"Token Liquidity and Volume Assessment"}]},"model":"claude-sonnet-4-6","version_no":5,"generated_at":"2026-05-21T15:57:22.506Z","provenance":"ai_authored_unreviewed","ai_authored":true,"merchant_reviewed":false,"merchant_edited":false,"merchant_reviewed_at":null,"merchant_edited_at":null,"skill_md_url":"https://x402gle.com/servers/defi.hugen.tokyo/SKILL.md","skills_url":"https://x402gle.com/servers/defi.hugen.tokyo/skills.json"}