Epsilon orders are signed messages executed by keepers. That design was for self-custody — but it has a second consequence: anything that can produce an EIP-712 signature can trade on Epsilon without touching our frontend. Today that becomes a product. The Epsilon developer platform is live, and it is built for AI agents first.

Self-serve API keys

Create a key at developers.epsilon.exchange, see your usage, and call the REST API for quotes, routes, token search, order placement, status and cancellation, plus market data. Reads work without a key where the data is public; anything that submits an order needs one. There is a complete OpenAPI spec, an llms.txt for agents that read documentation themselves, and a machine-readable error catalog so a client can decide whether to retry without a human.

MCP: trade from Cursor or Claude

@epsilon-exchange/mcp is a Model Context Protocol server. Point Cursor, Claude Desktop, Claude Code or any MCP client at it and the agent gets tools to search tokens, quote, preflight, place limit, stop-loss and DCA orders, and cancel them. Orders are signed locally with a wallet you configure — the key never leaves your machine — and two safety rails are on by default: a per-order spend cap that fails closed, and an optional explicit-confirm step before anything is submitted.

For research without a wallet there is also a hosted, read-only MCP at api.epsilon.exchange/mcp: quotes, routes, order books, market stats, docs search. It is listed in the official MCP registry, so a client that browses the registry finds Epsilon on its own.

SDKs for the signing part

Building an order correctly — maker traits, fee legs, trigger floors, salts — is the fiddly bit. The TypeScript and Python SDKs do exactly that and nothing more: fetch the route, build the order, sign it with your account, submit it. Both are verified byte-for-byte against the same test fixture the indexer uses, so a signature produced by the SDK is the signature the chain accepts. The MCP server is a thin layer over the TypeScript SDK; what the agent does, your bot can do.

Webhooks

Register an endpoint and receive HMAC-signed events for order-lifecycle changes — filled, partially filled, cancelled, expired. No polling loop, and the signature lets you reject anything that didn't come from us.

Permissionless rev-share

Every Epsilon fill carries a referral leg. If your integration routes flow through Epsilon with your referrer address in the order, that leg is paid to you on-chain, per fill, with no agreement to sign and no dashboard to be approved in. Build a bot, a dashboard or a Telegram group tool, and the fee share is simply part of the order you helped create.

Where to start

The quickstart places a limit order in about twenty lines. Runnable examples (a Python cron DCA, LangChain and Vercel AI SDK tools, a small Telegram bot) are in the examples repo and reachable from the MCP itself via list_examples. If you build something, tell us — the referral leg is already yours.