# Cambrian x402 API — EVM DEX Listings

> Cambrian x402 API — EVM DEX Listings is a paid API for AI agents from x402.cambrian.org, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Returns a list of decentralized exchanges (DEXes) available on EVM-compatible blockchain networks, paid per-call via x402 micropayment.

## Facts

- Endpoint: GET https://x402.cambrian.org/evm/dexes
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cambrian-x402-api-evm-dex-listings-04f0431e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ayqvh2amo52ZC4vkxBY-Z

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 cambrian-x402-api-evm-dex-listings-04f0431e
```

Example prompt: Pull the list of all decentralized exchanges available on EVM chains from Cambrian so I can see which DEXes I can route swaps through.

## When to prefer this

Use this endpoint when an AI agent needs a canonical, up-to-date list of EVM DEXes for routing, discovery, or dashboard population, and is operating in a pay-per-use x402 micropayment context. Prefer over manually maintained DEX lists when freshness and blockchain coverage matter.

## Known failure modes

- Payment not attached or insufficient — returns HTTP 402 requiring x402 USDC micropayment
- Invalid or unsupported query parameters — may return empty array or 400 error
- Network or upstream data provider outage — may return 500 or timeout
- Rate limiting if payment flow is misconfigured — returns 429 or 402

## How this service works

Pay-per-use blockchain and social data for autonomous agents.

## Output

An array of DEX objects, each describing a decentralized exchange available on EVM-compatible chains — likely including fields such as DEX name, protocol type (AMM, order book), contract address, and supported chain(s).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "queryParams": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "array"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "array"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cambrian-x402-api-evm-dex-listings-04f0431e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.cambrian.org](https://www.zero.xyz/host/x402.cambrian.org/llms.txt)