Nexwest exposes the order book as a public primitive. Builders can route orders, read state, stream data, and launch interfaces without asking for a listing or a market-maker relationship.
What you can build
| Category | Examples | Primitive |
|---|---|---|
| Trading interface | Mobile app, desktop terminal, embedded widget | Exchange + WebSocket |
| Execution | TWAP, chase, smart order router | Exchange + Info |
| Analytics | Dashboards, leaderboards, PnL tools | Info + historical data |
| Liquidity | Vaults, market-making bots | Exchange + vault API |
| Infrastructure | Indexers, oracles, alerting | WebSocket + EVM |
| Consumer | Copy trading, portfolio trackers | Info + signing |
The integration surface
- Public reads.
POST /infoand the WebSocket give you markets, books, candles, and account state. - Signed writes.
POST /exchangeplaces orders and manages margin. An API wallet scopes the permission. - EVM. Contracts can read Core state through precompiles and submit actions through CoreWriter.
- Builder codes. Attach a builder address and a fee to orders routed through your app.
Builder codes
A builder code is a fee share for the application that originated the order. It is not a referral code and does not require the user to sign up anywhere.
code
{
"type": "order",
"orders": [{ "asset": 0, "isBuy": true, "limitPx": "104000", "sz": "0.01", "reduceOnly": false, "tif": "Gtc" }],
"builder": { "b": "0xBuilderAddress", "f": 10 }
}f is in basis points: 10 = 0.01%. The maximum is 30 bps. The user must see the fee before signing; hiding it is a violation of the builder terms.
Fees are transparent
The builder fee appears in the order preview and in the fill record. Users can revoke a builder approval at any time from Settings → Approvals.
Getting started
- Read the API overview and authentication.
- Create a testnet API wallet.
- Fetch
metaand open a WebSocket book subscription. - Place a reduce-only order on testnet.
- Apply for a builder allocation if you need higher testnet limits.