# defi-dx DEX Volume API

> defi-dx DEX Volume API 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).

Returns DEX (decentralized exchange) trading volume data aggregated across supported blockchain chains.

## Facts

- Endpoint: GET https://defi-dx.hugen.tokyo/defi/dex/volume
- 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-c5463a4d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d1uS5rUor3Rg_h0zva2Tn

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-c5463a4d
```

Example prompt: Can you pull the current DEX trading volume data across all supported chains from the defi-dx analytics endpoint so I can see where the most on-chain activity is happening?

## When to prefer this

Choose this endpoint when you need aggregated DEX trading volume data across multiple blockchain networks in a single call. Ideal for DeFi analytics dashboards, on-chain market monitoring, or comparing decentralized exchange activity across chains. Prefer over manual chain-by-chain lookups when multi-chain volume aggregation is needed.

## Known failure modes

- Unsupported chain requested — returns empty or error response
- Payment not provided or insufficient — 402 Payment Required
- Network connectivity issues — request timeout
- Rate limit exceeded — too many requests
- Service unavailable — 503 or 5xx error

## How this service works

Returns DEX trading volume data across supported chains.

## Output

Returns DEX trading volume figures broken down across supported blockchain chains, providing quantitative volume metrics for decentralized exchange activity on each network.

## Example request

```json
{
 "method": "GET"
}
```

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ]
  }
 }
}
```

## 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-c5463a4d/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)