One API for
perpetual
futures
The Nexus Exchange lists BTC, ETH and SOL perpetuals on one cross-margined dollar account. Every order is a signed REST or WebSocket call, margin is checked inside the matching engine, and the terminal is one client of the API.
In Partnership With
0G
AISeer
Aimo
Alchemy
Aligned
Autonomys
Avail
Babylon
BCW
Billions
Bitget
Caldera
CertiK
Clique
CodeStream
Cudos
Cycle
Cysic
Doppelgangers AI
DTEAM
Investors
How it works
One request,
one engine
Every client calls the same API. Each order passes through one engine that checks its margin, matches it and settles the fill to a dollar balance.
Who calls it
- Market makers
- Quant and pro traders
- Developers building on the Exchange
- Agents
Nexus API
- 01Order entrySigned REST and WebSocket requests
- 02Pre-trade riskMargin checked before an order is accepted
- 03MatchingCentral limit order book, price-time priority
- 04Margin and liquidationOne cross-margined account across every position
- 05SettlementFills settle to your dollar balance
What it reaches
- BTCPerpetual
- ETHPerpetual
- SOLPerpetual
Why Nexus
Built for
trading systems
What a desk checks before it connects: the API surface, the order handling and the risk model.
- 01
API first
Anything the terminal does is a REST or WebSocket call, and some API capabilities have no screen at all. Public market data needs no key.
- 02
One dollar account
A single dollar balance cross-margins every BTC, ETH and SOL position you hold, under one risk model.
- 03
Quote, amend, pull
Post-only rejects rather than crossing. Refresh a ladder in one batch request, amend price and size in place, and clear a market with one cancel-all.
- 04
Risk inside the engine
Margin is checked inside the matching engine before an order is accepted, not reconciled after the fill.
- 05
Errors a program can read
Every refusal carries a stable, machine-readable code, and an order's client ID means a retry never places it twice.
- 06
Bring your stack
Rust, Python, TypeScript and Go SDKs sign requests for you, there is a CLI over the Rust one, and CCXT-compatible endpoints are live for market data.
Who it's for
For anyone
trading by code
Market makers
Quote both sides with post-only and batch requests, and pull a whole market with one cancel-all.
Quant and pro traders
Run strategies on the same API the terminal uses, from the language you already work in.
Developers building on the Exchange
Anything the terminal does is in the API, the SDKs and the CLI, so you build on the same surface it runs on.
Agents
Connect an agent through the MCP server and agent skills, and point it at llms.txt to read the docs.
Developers
How to connect
Start with the API: anything the terminal does is a REST or WebSocket call, and public market data needs no key. The SDKs, the CLI, the MCP server and agent skills are open-source clients of the same API.
Prefer to trade on screen?
The Nexus terminal is one client of the same API. Connect a wallet and trade the same books by hand, with a chart, an order book and the order ticket.
Partner
With Us
We work with market makers, liquidity providers, and the teams listing the next asset class. Tell us what you trade and we'll find the shortest path to a book.
Join Us
We're building a trading venue that has to beat the best exchanges in the world at matching, at risk, and at latency. If that's the sort of problem you want, we're hiring.