Four ways to put event contracts in front of your traders.
Take the hosted app, embed widgets in the surface you already have, ship the mobile SDK inside your app, or build against FIX and REST yourself. Most operators use two of the four.
{{ s.t }}
{{ s.k }}{{ s.d }}
The trader terminal, out of the box.
Watchlist, chart, book, ticket and positions, restyled per tenant, on desktop and in the mobile app. This is the default skin.
Simulated data. Layout and fields as shipped.
Three protocols, chosen by what you are building, not by plan tier.
Nothing here is gated behind a plan. Select a protocol to see what it covers and a representative call.
{{ protoTitle }}
{{ protoTag }}{{ protoBody }}
Bolt-on or full integration. Any vendor quoting one number has not asked about your ledger.
Both tracks share the same five integration points. What differs is how much of your stack they touch, and therefore who has to be in the room.
Three embeddable surfaces, styled from your tokens.
Colour, radius, type and density come from a token file you control, so the widget looks like your product rather than ours. No iframe styling fights.
Single-contract widget
Embedded previewSimulated prices. One script tag, one data attribute for the market id, and your token file.