# LensCrypt Arbitrage Tokens & DEX Directory

> LensCrypt Arbitrage Tokens & DEX Directory is a paid API for AI agents from lemscrypt.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Returns the list of supported tokens and decentralized exchanges (DEXes) available for arbitrage opportunity scanning.

## Facts

- Endpoint: GET https://lemscrypt.vercel.app/api/arb/tokens
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lenscrypt-arbitrage-tokens-dex-directory-a406fb0c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vuDhLeY1kHcFahHCgV8A_

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 lenscrypt-arbitrage-tokens-dex-directory-a406fb0c
```

Example prompt: Show me all the tokens and DEXes that LensCrypt's arbitrage scanner supports so I can figure out which trading pairs I can monitor for price differences.

## When to prefer this

Use this endpoint when you need to discover what tokens and DEXes are eligible for arbitrage scanning before querying live arbitrage opportunities, or when validating that a specific token or exchange is supported by LensCrypt's arb engine.

## Known failure modes

- Payment not received or invalid x402 payment header — returns 402 Payment Required
- Service unavailable or Vercel cold-start timeout — returns 5xx error
- Unexpected empty list if the underlying token/DEX registry is not populated

## How this service works

Supported tokens and DEXes for arbitrage scanning.

## Output

A structured list of tokens (with symbols and possibly contract addresses) and decentralized exchanges (DEXes) that the LensCrypt arbitrage scanning engine supports, enabling the caller to know what assets and venues can be monitored for price discrepancies.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lenscrypt-arbitrage-tokens-dex-directory-a406fb0c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lemscrypt.vercel.app](https://www.zero.xyz/host/lemscrypt.vercel.app/llms.txt)