Venue adapter SDK

Builders add new venues so coverage grows beyond what Mutexa ships.

Purpose

Every venue has its own interface. The Venue adapter SDK lets builders add new venues so coverage grows beyond what Mutexa ships, while slicing, the band, rails and the risk engine stay shared.

What an adapter is responsible for

Market data: DescriptionPrices and market rules the planner needs to size slices and compute the band.

Placing and closing: DescriptionOpening, adjusting and closing a slice through the venue's own interface.

Margin and repayment: DescriptionAdding margin to a perp slice or repaying a loan slice when the risk engine asks.

Position state: DescriptionReporting each slice's size, health and liquidation price back to the device.

Fee path: DescriptionUsing the venue's integrator program where it exists, or a separate path where that would hurt privacy.

Responsibility	Description
Market data	Prices and market rules the planner needs to size slices and compute the band.
Placing and closing	Opening, adjusting and closing a slice through the venue's own interface.
Margin and repayment	Adding margin to a perp slice or repaying a loan slice when the risk engine asks.
Position state	Reporting each slice's size, health and liquidation price back to the device.
Fee path	Using the venue's integrator program where it exists, or a separate path where that would hurt privacy.

What stays out of an adapter

Open source

The client, the venue adapters and the slicing logic are planned to be open source on the official GitHub at github.com/mutexa-labs, so new adapters can be reviewed in public.