This page is the starting point for builder integrations. Builders typically care about two things first:Documentation Index
Fetch the complete documentation index at: https://docs.ostium.com/llms.txt
Use this file to discover all available pages before exploring further.
- how to attach builder fees to trades
- which client mode matches the way their product handles signing and submission
Builder fees
Builder fees are configured once at client creation and then applied automatically to opening trades sent through that client.builder.addressis where your fee share is routedbuilder.feeBpsis the fee amount in basis points- the allowed range is
0to50bps - builder fees apply on open, not on close
builder config entirely.
Which client mode to use
Wallet-driven frontend
Useself-self when the user signs and pays gas in their own wallet.
Use self-gasless when the user should still own the account but you want gasless trading after one-time setup.
This is usually the right fit for:
- React apps
- embedded trading widgets
- client-side wallet integrations
Backend execution on behalf of users
Usedelegated-self when your backend should sign and submit using a delegate EOA that pays gas.
Use delegated-gasless when your backend should sign but submit through a Safe user operation.
This is usually the right fit for:
- managed execution products
- server-side order routing
- apps that want users to keep custody while your backend handles execution
Read-only market data
UsecreateReadOnly() when you only need prices, pairs, positions, candles, or order history in your app and you do not need transaction building or submission.
Recommended path
- Start with SDK Overview for the current API surface.
- Use Client Modes to choose the right mode for your integration.
- Use Getting keys from the App if you want users to export a delegated gasless SDK account from
app.ostium.com/sdk-export. - Use React Example if your app needs wallet-driven transaction building and live position updates.