For engineering teams
Engineered to be reviewed, not taken on trust.
Adaptic OS runs on a versioned REST API and an ordered event stream. Every call carries a short-lived token and is checked against the caller’s role, and every order meets the same pre-trade checks, whichever path it takes. Walk through it with our engineers.
Every message on the stream shares one envelope: the event, its data, the account, a correlation ID that ties it to the action behind it, a timestamp and a sequence number.
Clear interfaces. Controlled access.
Event stream
Events you can count on.
Positions, orders, trades, quotes and risk arrive on one stream as they happen. Every message is numbered, so your client knows the moment it misses one.
REST API
One versioned API.
Accounts, orders and fills, portfolio, risk and alerts, under one versioned REST API with an OpenAPI reference after sign-in.
Access
Access by role.
Roles from admin to read-only decide what each caller may see and do. A read-only role cannot place or cancel anything.
No long-lived keys. By design.
Tokens, not keys.
API-key authentication was removed on purpose. A request with a key is refused and told to present a signed token.
Every call is authenticated.
That includes the API reference; only the redacted public status page is open. The web layer adds strict transport security, a content security policy, cross-site request protection and rate limiting.
Broker keys stay with the system.
Only Adaptic’s internal service identity can read stored broker and vendor keys. No user, browser or anonymous caller can read them, or filter or sort on them.
What is recorded.
Failed sign-ins, operator actions, and every write through the data service, with actor, time and changed fields. Stored credentials are redacted from the record.
GET /api/v1/portfolioX-API-Key: sample_key_… 401 Unauthorized{ "error": { "code": "API_KEY_AUTH_UNSUPPORTED", "message": "API key authentication is not supported; present an engine-issued JWT (Authorization: Bearer <jwt>)" }}An API call proposes. The checks decide.
An order sent through any interface meets the same pre-trade checks and the account’s trading policy as an order from the engine. Each order client is bound to one account and refuses if that account’s trading is off, and the entry halt blocks anything that adds risk while exits and protective stops go through.
Every event ordered. Every event traceable.
Every message on the stream shares one envelope: the event, its data, the account, a correlation ID that ties it to the action behind it, a timestamp and a sequence number.
Start with an engineer, not a key.
- BriefingWe walk your engineers through the API, the event stream and the security model.
- Shadow pilotSix weeks. Your mandate is written in Mandate Studio and your brokerage account is connected in Adaptic OS. Access to the OS opens with the pilot.
- ConnectionsBrokerage, market data and language models connect through one integration layer, governed by the same checks.
Walk through it with our engineers.
Bring the systems you want to connect. We show you the interfaces, the security model and the event contract your systems would read.