# 100BTC DEX Trade Route Optimizer

> 100BTC DEX Trade Route Optimizer is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Returns an optimal DEX split routing strategy for a token swap, including recommended exchange shares and estimated savings/slippage metrics

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/router?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-dex-trade-route-optimizer-d5c9c212
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_33_PYdwzl-UkTNfUgEvEm

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 100btc-dex-trade-route-optimizer-d5c9c212 -d '<json body>'
```

Example prompt: What's the best way to split a $500 swap from USDC to VIRTUAL across DEXes to minimize slippage — can you show me the recommended exchange breakdown and estimated savings?

## When to prefer this

Use this endpoint when an AI agent needs to pre-compute an optimal multi-DEX trade route before executing a token swap, particularly for amounts large enough that splitting across venues yields meaningful slippage savings. Prefer this over single-DEX quote APIs when the goal is minimizing price impact across Aerodrome, Uniswap v3, and other supported venues simultaneously.

## Known failure modes

- Unsupported token pair returns an error or empty routing result
- Amount too small to meaningfully split across DEXes may return single-DEX recommendation
- Stale liquidity data may cause suboptimal routing suggestions
- Network or payment (x402) failure returns HTTP 402 or 5xx
- Invalid token symbol format causes schema validation error

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

Returns a JSON object with a recommended_split array listing each DEX and its suggested share of the trade, plus metrics including estimated savings in USD and blended slippage percentage for the proposed routing strategy.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token_in": {
   "type": "string"
  },
  "token_out": {
   "type": "string"
  },
  "amount_in_usd": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "metrics": {
   "est_savings_usd": 42.5,
   "blended_slippage": "0.047%"
  },
  "token_in": "USDC",
  "token_out": "VIRTUAL",
  "recommended_split": [
   {
    "dex": "Aerodrome Finance",
    "share": "65%"
   },
   {
    "dex": "Uniswap v3",
    "share": "35%"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-dex-trade-route-optimizer-d5c9c212/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)