Brokers

Anthid connects to brokers on your behalf, so your systems deal with one interface instead of one per broker. Each broker has its own way of expressing an order, its own error vocabulary, its own connection behaviour, and its own rules about what it will accept. Connecting directly means learning and then permanently maintaining all of that, once per broker. Anthid absorbs it. Once a broker account is connected, it works the same way as every other: the same order submission, the same controls, the same live updates, and the same historical record.

​

Supported Brokers

Additional broker integrations will be added over time based on platform priorities and customer demand.

​

Integration stability

Each broker integration carries a stability level that describes how far along its production readiness is. The level applies to the broker integration itself. The platform APIs in front of it (intents, controls, streaming, ledger) are versioned and documented separately.

​

Stability levels

​

Service levels

Broker integrations carry no service level commitment, at any stability level. No uptime, latency, throughput, or recovery target is committed for a broker integration, and its behavior is not covered by production support terms. Stability describes how hardened an integration is and how far ahead its changes are communicated — see Integration stability. It is not a level of service commitment, and reaching general availability does not add one. This applies to the broker integration layer specifically. Platform services in front of it (intents, controls, streaming, and ledger) are governed by their own terms.

​

What beta means in practice

Both current integrations are in beta. When building against them:

• Everything documented on a broker page is implemented and routed end to end. Gaps are called out explicitly rather than left silent. See the capability matrices in Supported Order Types, Supported Destinations, and Supported Time In Force.
• Broker-side behavior at the edges is still being hardened and may change as cases are found and fixed. This covers routing rejections, replace and cancel semantics, time-in-force handling, and reconnection during a session.
• Capability coverage grows during beta. New order types, routes, and time-in-force values are added to a broker integration as they are validated.
• Validate a strategy against a paper trading account before connecting a live one, and configure risk controls before the first live intent.
• No service level is committed for a beta integration, or for any integration. See Service levels.
• Report unexpected broker behavior to support@anthid.com. Beta feedback directly shapes what is hardened next.

​

Unified Platform Layer

All supported brokers integrate with the same Anthid platform services. This allows applications to use a consistent interface for:

• Trading account management
• Intent submission
• Risk and trading controls
• Order and position tracking
• Real-time event streaming
• Historical ledger queries

Broker-specific capabilities and limitations remain documented on each broker’s individual page.

​

Broker Capabilities

Supported functionality varies between brokers, and Anthid does not paper over the differences. An order using something the target broker does not support is refused rather than quietly altered. Other differences include available order types, market access, rate limits, and extended-hours support. The full matrices are in Supported Order Types, Supported Destinations, and Supported Time In Force.

​

Environments

Where supported by the underlying broker, Anthid supports both paper and live trading environments. Applications can connect multiple trading accounts and operate across different environments simultaneously through the same platform APIs.

​

Rate Limits

Anthid applies platform-level rate limits while respecting the capabilities of each broker integration. Effective throughput may vary depending on broker-specific restrictions, exchange requirements, and account-level limitations.

​

Why this is worth outsourcing

Getting an order to a broker is the easy part of a broker integration. What follows is the expensive part, and it does not end: keeping credentials safe, keeping the connection alive and recovering it when it drops, translating between your model and the broker’s, noticing when the two have drifted apart, and being awake when any of that fails during a trading session. None of that work differentiates your firm. It is a running cost that has to be staffed rather than a project that gets finished, and it doubles the day you add a second broker. Anthid runs it as managed infrastructure, so the question of which broker to trade through becomes a commercial decision rather than an engineering project.