Order plumbing,
by API
Settlement dates, order-state validation and pre-trade checks, as typed records for the systems that move orders.
Three surfaces, one order
Each returns a typed record the order system can act on.
Settlement dates
T+1 from the trade date, across weekends and holidays.
Order states
Each event checked against the last; the odd one flagged.
Pre-trade checks
Session, lot and tick size, checked before the venue does.
Three acts stay with registered firms
A call that reaches one gets a typed BLOCKED, naming the firm it belongs to.
Checks and dates for the systems that move orders. Never the order itself.
Who builds on it
The engineers behind the systems that move orders, never the trader.
- Execution engineering
Validates every order event before it is booked.
- Broker-dealer operations
Knows the settlement date before the trade is booked.
- Trading platforms
Rejects sub-penny prices before the venue does.
- Risk and compliance
Replays an order’s states for the audit trail.
One key, every door
This door answers for itself, on the family key.
Request access
Tell us what you’re building, which surface first and how many orders you handle.
Received.
We’ll reply by email.