Sequence/docs
THE TRADING OS

Welcome to Sequence Markets

The execution kernel for institutional crypto trading. Connect exchange accounts, route orders across 12 venues with SOR, deploy WASM strategies at the edge, and track every fill through one API.

Start here


Choose an interface

Python SDK

Zero dependencies. from sequence_markets import Sequence.

Rust SDK

Typed builders, async/await, WebSocket streaming.

CLI

sequence connect binance, then sequence buy ETH-USD 50.

REST API

Every endpoint curl-friendly. Full reference with examples.

MCP (Claude)

80 tools exposed to AI assistants. Analyze, monitor, trade.

Terminal

Browser dashboard — charts, order entry, live execution.


What Sequence does

You want to buy 200 ETH. Best execution isn't on one exchange — it's split across three. Binance has depth at $2,325, Coinbase at $2,326, Kraken at $2,327. Without an execution layer: three connections, three order books, three reconciliations.

With Sequence:

python
from sequence_markets import Sequence
 
seq = Sequence("seq_live_...")
order = seq.buy("ETH-USD", 200, urgency="medium")
# SOR splits across Binance + Coinbase + Kraken automatically

Or a single HTTP call:

bash
curl -X POST https://api.sequencemkts.com/v1/orders \
  -H "Authorization: Bearer $SEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"symbol": "ETH-USD", "side": "buy", "qty": 200}'

The SOR evaluates every connected venue, computes the optimal split across price / fees / depth / latency, executes all legs simultaneously, and streams fills back to you.


The product ladder

Every feature maps to a level. You get value at Level 0. Each level builds on the one below — and lower levels are never gated behind higher ones.

LevelNameWhat you can doTime to value
0ConnectPlug in exchange API keys30 seconds
1SeeUnified quotes, balances, positions across all venues1 minute
2TradeSmart order routing, market / limit via CLI, SDK, or API5 minutes
3OrchestrateExecution graphs: multi-leg orders, conditional triggers, risk policies10 minutes
4AutomateWASM algorithms on venue edges, backtesting, deployment1 hour
5MeshCross-venue algo instances with sub-millisecond IPCDays
Tip

You don't need to write code. Levels 0–2 work entirely through the CLI or API. Levels 4–5 are for quants who want microsecond-latency execution.


How it works

  1. You send an order — via Python / Rust SDK, CLI, REST API, or MCP.
  2. It becomes an execution graph. A market buy is a 1-node graph. A spot + perp hedge is a 2-node graph with dependency edges. Every order uses the same primitive.
  3. The SOR routes each node. Evaluates every connected venue for price, fees, depth, and latency. Splits across the best venues.
  4. Edge servers execute. Dedicated servers co-located near each exchange handle the venue protocol. For WASM algos, your strategy runs directly on the edge.
  5. Fills stream back. Real-time via WebSocket. The graph engine tracks dependencies: when node A fills 50%, node B activates automatically.

Build with Sequence