Introduction to Anthid

Anthid provides order and execution management through an API and a web dashboard. It sits between the systems your firm uses to trade and the brokers those trades go to. Your strategy decides what to trade; Anthid records the instruction, routes it to a connected broker, and tracks the result. Your systems send an order to Anthid. Anthid checks it against the limits you have configured, passes it to the connected broker, reports back what the broker did with it, and keeps a record of the whole exchange.

​

What sits between you and the broker

Connecting a firm’s systems directly to a broker means building and then permanently staffing a set of things that have nothing to do with your strategy: somewhere safe to keep broker credentials, code that keeps the connection alive and recovers when it drops, a place to enforce risk limits, a record of what was traded, and a way to see it all. Anthid provides those as a service. Your systems talk to one interface, and Anthid deals with each broker’s particulars behind it.

​

Trading accounts

A trading account is one broker account connected to Anthid. It belongs to your organization, holds the broker credentials in encrypted storage, and is the thing everything else attaches to: orders, positions, limits, and connection health. Anthid keeps each connection open and reports whether the broker is currently reachable, so you can check before trading or show it on a dashboard.

​

Orders, and what you asked for

Anthid keeps two records where most broker APIs keep one. An intent is what you asked for: the instruction as your system sent it, recorded before Anthid contacts the broker at all. An order is what came of it at the broker. Keeping them apart is what lets the platform answer the awkward questions. If a broker is unreachable, rejects the order, or acknowledges it and then goes quiet, the instruction still existed, was authorized, and was acted on. A record that only begins once the broker accepts cannot describe that gap. The same separation is what makes an instruction broker-agnostic. You express an order in Anthid’s terms, and it is translated into each broker’s dialect when it is routed. The instruction reads the same whichever connected broker it goes to.

​

Controls

Anthid evaluates your configured limits before accepting a new CREATE instruction. Replacements and cancellations do not run this evaluation, and disabling trading does not cancel orders already at a broker. You can stop trading across the whole organization with a single switch, or restrict a single account or a single symbol. Limits cover order size, trading hours, and outright enable and disable. Changes take effect without anyone redeploying an application, which matters most on the day you need to stop something quickly. Controls give supervisory constraints somewhere to live besides the trading application itself, and the constraint is enforced whether or not the application remembered to check.

​

Live updates and history

Broker updates reach your systems as Anthid receives them rather than on a polling interval, so an application can react to a fill or a rejection when it happens. Everything also lands in the ledger, a durable record of orders and positions that stays queryable afterwards. That is what reporting, reconciliation, and a supervisory review read from, and order and position records are retained for six years. Your plan determines how much history you can query through the API. See Limits and entitlements.

​

What a firm uses this for

• Put firm-wide risk limits in front of every order regardless of which system sent it
• Block new create instructions across connected accounts with an organization kill switch
• Answer what was traded, by which system, and under whose credential
• Feed internal dashboards, reporting, and reconciliation from one record
• Trade multiple broker accounts, paper and live, through one integration
• Add or change brokers without rebuilding the systems that trade through them

​

Next steps