# TokenGuard Exchange Volume API

> TokenGuard Exchange Volume API is a paid API for AI agents from eltociear-tokenguard.hf.space, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Retrieves trading volume data for cryptocurrency exchanges via the TokenGuard DeFi analytics platform

## Facts

- Endpoint: POST https://eltociear-tokenguard.hf.space/exchange_volume
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tokenguard-exchange-volume-api-b67d9455
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0-AITVxCrn_TFRSn9paX1

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 tokenguard-exchange-volume-api-b67d9455 -d '<json body>'
```

Example prompt: What's the trading volume on Uniswap over the last 24 hours? Pull it from TokenGuard's exchange volume endpoint.

## When to prefer this

Choose this endpoint when you need on-chain DEX or exchange trading volume data as part of a broader DeFi analytics workflow, especially if you are already using the TokenGuard suite for ERC-20 safety checks or other DeFi metrics. It is best suited for AI agents that pay per call via x402 micropayments on Base and need programmatic access to exchange volume without a heavy subscription.

## Known failure modes

- Invalid or unsupported exchange identifier returns an error or empty result
- Missing required parameters cause a 400-level response
- Payment failure via x402 micropayment protocol blocks the request
- HuggingFace Space hosting may introduce cold-start latency or downtime
- Unsupported chain or time range returns empty or partial data

## How this service works

exchange volume data for AI agents.

## Output

Returns JSON containing exchange volume metrics for the queried DEX or protocol, likely including volume figures (in USD or token amounts), time-period breakdowns, and exchange identifiers. The exact schema is minimally documented but follows the TokenGuard DeFi analytics data model.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [],
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tokenguard-exchange-volume-api-b67d9455/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from eltociear-tokenguard.hf.space](https://www.zero.xyz/host/eltociear-tokenguard.hf.space/llms.txt)