# DeFi Protocol Directory - defi-dx.hugen.tokyo

> DeFi Protocol Directory - defi-dx.hugen.tokyo is a paid API for AI agents from defi-dx.hugen.tokyo, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Lists DeFi protocols available across supported blockchain chains with pagination support.

## Facts

- Endpoint: GET https://defi-dx.hugen.tokyo/defi/protocols
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-dx-hugen-tokyo-68d28308
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HOooRcgnRXf0YiXy3OOTf

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability defi-dx-hugen-tokyo-68d28308
```

Example prompt: Show me the first 20 DeFi protocols available across supported chains on defi-dx.hugen.tokyo — page 1 with a page size of 20.

## When to prefer this

Use this endpoint when you need a directory or index of DeFi protocols across multiple chains, especially as part of a DeFi aggregator workflow. Prefer this over chain-specific endpoints when you want a cross-chain protocol overview. Useful as a discovery step before querying volumes or stablecoin data on specific protocols.

## Known failure modes

- Invalid page or pageSize parameters return error
- Payment of $0.01 USDC required per call via x402 — missing payment results in 402 response
- Very large result sets may be truncated if pagination is not used properly
- Unsupported chain filters may return empty results

## How this service works

Lists DeFi protocols across supported chains.

## Output

A paginated list of DeFi protocols available across supported blockchain chains, including protocol metadata. The response can be large (example shows ~7.7MB untruncated), so pagination parameters are essential.

## Example request

```json
{
 "page": 1,
 "pageSize": 20
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "page",
  "pageSize"
 ],
 "properties": {
  "page": {
   "type": "number"
  },
  "pageSize": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "_bytes",
  "_preview",
  "_truncated",
  "_contentType"
 ],
 "properties": {
  "_bytes": {
   "type": "number"
  },
  "_preview": {
   "type": "string"
  },
  "_truncated": {
   "type": "boolean"
  },
  "_contentType": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-dx-hugen-tokyo-68d28308/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from defi-dx.hugen.tokyo](https://www.zero.xyz/host/defi-dx.hugen.tokyo/llms.txt)