DexL Agents

Official registry Search and web

Pay-per-call AI gateway: models, speech, web search, on-chain reads and NLP tools, via x402.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http dexl-agents 'https://agents.dexl.io/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "dexl-agents": {
            "type": "http",
            "url": "https://agents.dexl.io/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Pay an API with x402 — in about ten lines
  2. 1. Free: no wallet at all
  3. 2. Paid: one call, one signature
  4. 3. Connect an MCP client
  5. What you can call

Pay an API with x402 — in about ten lines

x402 is HTTP 402 put to work: a server answers 402 Payment Required with the exact price, the client signs a stablecoin payment and repeats the same request. No account, no API key, no invoice.

These examples call DexL Agents, an x402 gateway (chat models, speech, web search and crawl, on-chain reads, FX rates, NLP tools). Everything here works against any x402 server — only the URL changes.

1. Free: no wallet at all

npm install
npm run free

free.mjs does two things:

  • calls the free tier (model: "dexl-free") — no payment header, no wallet, no account;
  • asks what a paid call would cost by sending it without payment and reading the 402.

Real output:

free answer: HTTP 402 (Payment Required) is a non-standardized status code reserved for future use...
web-search costs 0.01 USDC on eip155:8453 (HTTP 402)

2. Paid: one call, one signature

PRIVATE_KEY=0x... npm run paid

The payment is these three lines; after them it is ordinary fetch:

const signer = toClientEvmSigner(wallet);
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(signer));
const fetchWithPay = wrapFetchWithPayment(fetch, client);

Your key stays on your machine — the server only ever sees a signed payment. Settles in USDC on Base, Polygon, Arbitrum or Solana. Error responses are not charged.

The free example above was run as-is. The paid one needs your own funded wallet, so run it yourself with a small balance; it uses the same client our own service uses.

3. Connect an MCP client

Remote (free tools only — a remote server holds no wallet of yours):

https://agents.dexl.io/mcp

Local, with paid tools, because the wallet stays on your machine:

{
  "mcpServers": {
    "dexl": {
      "command": "npx",
      "args": ["-y", "dexl-agents", "mcp"],
      "env": { "DEXL_BASE_URL": "https://agents.dexl.io", "DEXL_PRIVATE_KEY": "<optional>" }
    }
  }
}

What you can call

GET /v1/tools lists every tool with its price and schema. Machine-readable: /llms.txt · /openapi.json · /.well-known/x402 · /.well-known/mcp

MIT licensed. Issues and pull requests welcome.

Frequently asked questions

What is DexL Agents?

Pay-per-call AI gateway: models, speech, web search, on-chain reads and NLP tools, via x402.

How do I install DexL Agents?

It runs as a remote server. In Claude Code: claude mcp add --transport http dexl-agents 'https://agents.dexl.io/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does DexL Agents need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is DexL Agents open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains DexL Agents?

It is published by dexl-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.