What you can build
- An evaluations business — issue accounts in batches of up to 20, each tied to a trader’s sign-in email and your own
referenceId, with one bad email failing only its own item. - Risk that enforces itself — five controls per account (daily and weekly loss, daily and weekly profit, an end-of-day close 1–240 minutes before the bell), live from the moment you write them; a control that fires flattens and locks the account.
- The full lifecycle — halt trading, resume it, reset an evaluation to its starting state. A halt blocks new orders without closing anything; only a reset gets the account flat.
- A ledger you can audit — record balance operations for payouts, credits and corrections, each keyed on your own reference so a retried pipeline can never pay out twice.
- Billing you can reconcile — read your usage and the accounts behind it, from the same query the invoice is computed from.
- A back office that stops polling —
account.reset,balance.recorded,risk.lockedandrisk.unlockeddelivered to your server as they happen.
Core objects
An issued account, its risk controls, and a balance operation. All under Firm accounts in the reference. The usage reads sit under Connect, because the meter is one meter however the account arrived.Where to go next
Run firm accounts
The whole surface in one short tour, one call per step.
Issue evaluation accounts
The batch shape, the per-item results, and what balance means.
Govern account risk
Five controls, and halt versus resume versus reset.
Record balance operations
Payouts, credits, corrections, and the ledger they land on.
Read your usage
What the meter counts, and how to reconcile an invoice.
Connect Overview
Registering accounts you issued at your own venue — the same surface a broker uses.
Receive events
Signed deliveries, retries, and the delivery log.
Two ways in
This path beside the other one, and when a firm uses each.