Strategy API

Run your own bots and algos through Mutexa slices on any supported venue.

Overview

The Strategy API lets your own bots and algos trade through Mutexa slices on any supported venue. Your code decides what to trade. Mutexa handles the split, the band, funding through the rail and the risk engine, so the strategy is never readable from one public wallet.

Core concepts

Position: MeaningWhat your strategy wants: venue, market, side, total size and leverage, or a loan.

Plan: MeaningHow Mutexa would split it: slices, sizes, margin or loan-to-value, the band, cost and linkability.

Slice: MeaningOne part of the position, held by one fresh, unlinked account.

Book: MeaningEvery open position across venues and chains, aggregated on your machine.

Concept	Meaning
Position	What your strategy wants: venue, market, side, total size and leverage, or a loan.
Plan	How Mutexa would split it: slices, sizes, margin or loan-to-value, the band, cost and linkability.
Slice	One part of the position, held by one fresh, unlinked account.
Book	Every open position across venues and chains, aggregated on your machine.

The shape of a call

The flow mirrors the app: describe a position, review the plan, then confirm. The example below shows the shape only. The published interface ships with the SDK.

strategy.tsIllustrative interface

// Describe what you want. Mutexa decides how to split it.
const plan = await mutexa.plan({
  venue: "hyperliquid",
  market: "BTC-PERP",
  side: "long",
  size: totalSize,
  leverage,
});

// Check before you commit.
plan.band;          // liquidation levels across slices
plan.linkability;   // how easily the slices could be clustered
plan.cost;          // extra fees, rail costs and time

await plan.confirm(); // funds through the rail, opens slice by slice

Network privacy

API traffic can be routed through Tor so your IP doesn't tie the slices together. Keys stay on the machine running your strategy, the same as in the app.