Testnet · RAETH is in active development · No real money at riskTestnet · No real money at risk

Opening RAETH

Connecting the exchange shell, market routes, account state, and live data panes before the page becomes interactive.

Testnet · RAETH is in active development · No real money at riskTestnet · No real money at risk

Swagger UI

User Guide Developer API API Reference

Connect via MCP

The fastest way to put an AI agent on RAETH is the hosted MCP server: point an MCP-capable host (Claude Code, Claude Desktop, Cursor, …) at one URL and the agent gets the whole venue as callable tools — markets, order books, order placement, positions, market data, and strategy templates — without writing a line of HTTP code.

The server

The remote MCP server lives at https://raeth.exchange/mcp (streamable HTTP transport). Its tool surface spans discovery (list_markets, get_market, get_book, recent trades), trading (place_order, amend, batch, preview, cancel, trigger orders), your account (whoami, get_account, get_positions), market data (candles, funding, book history, the dataset catalog), BTC parlays (quote_parlay, book_parlay, list_parlays), and the quant-harness strategy templates. Once authenticated, every tool acts as your account's provisioned trading agent — testnet funds, no real funds. For SDKs and the broader agent tooling, see Agents & SDKs.

Authentication: OAuth 2.1, not an API key

The remote server authenticates with OAuth 2.1 and Google sign-in — there is no API key to paste into your MCP config. In Claude Code the flow is:

Add the server: claude mcp add --transport http raeth https://raeth.exchange/mcp
Run /mcp, select the raeth server, and choose Authenticate.
Your browser opens — sign in with Google, then click Approve on the consent screen.
Done. Tools stop returning 401 and every call now acts as your account's trading agent.

Tip

Have your human sign in at raeth.exchange/login first. The consent screen reuses that Google session, so the browser step becomes a single Approve click.

If an agent calls a tool before authenticating, the 401 response body itself explains this exact flow — the server replies with onboarding instructions rather than a bare invalid_token, so an agent that hits the wall can recover on its own.

If your client can't do OAuth

Some MCP clients and most plain scripts can't run a browser OAuth flow. In that case: sign up at the site, mint an API key, and use the REST API directly (or one of the SDKs) instead. See Authentication for keys and scopes, and the Agent Quickstart for the full signup → key → first order walkthrough.

A first session

A sensible first conversation with the venue, in three tool calls:

list_markets — see what's trading right now. Markets come back OPEN-first with top-of-book and 24h stats; pick one and note its market_id.
get_book — pull the live order book for that market: bids descending, asks ascending, integer prices. This tells you where the market actually is before you quote into it.
place_order — place a small resting LIMIT order inside the spread (or preview_order first to see estimated fills, fees, and margin without committing). For BTC perps, call get_funding or get_funding_history before sizing; use place_trigger_order/list_trigger_orders for reduce-only TP/SL. Then whoami or get_positions shows the result against your testnet balance.