Introduction

Documentation Index

Fetch the complete documentation index at: https://docs.anthid.com/llms.txt

Use this file to discover all available pages before exploring further.

Anthid gives teams a faster way to build broker-connected trading systems without taking on the heavy infrastructure work. Instead of building and maintaining your own broker client manager, risk control platform, streaming layer, ledger, and metrics pipeline, you can connect through Anthid and focus on the trading workflows that matter to your product.

​

Platform concept

Anthid sits between your application and a linked broker account. Your application sends a request to the platform, Anthid records the request, applies the configured controls, routes it to the connected broker, and returns broker responses back to your integration. The result is a managed trading control plane: one place to accept actions, enforce guardrails, route broker traffic, stream updates, store activity, search historical records, and measure what happened. That is a lot of critical infrastructure you do not have to design, operate, and constantly patch yourself.

​

Intents

An intent is a request for the platform to perform an action against a linked broker account. When an intent is accepted, it becomes the platform record of truth for the action Anthid agreed to relay. The intent captures what your application requested, which broker account it targets, which controls were evaluated, and the action that should be performed.

​

Broker routing

After Anthid accepts an intent, the platform routes the trade or account action through the connected broker. Anthid manages the broker connectivity layer for you, so your team does not need to build and maintain custom broker clients, reconnection logic, routing code, and response handling for every integration. The broker response is received by Anthid and associated back to the original intent so your application can trace the full lifecycle of the request.

​

Real-time updates

Broker responses are relayed back to your application through the connected gRPC client as soon as they are received. This lets your integration react to accepted orders, rejected orders, fills, and other broker events without waiting for polling. Anthid also gives you more flexible client connectivity on top of broker limitations. Where a broker may expose a single streaming connection, Anthid can support hundreds of downstream client connections and multiplex updates through the managed broker connection.

​

Ledger and metrics

Responses and trade events are stored in a ledger after they are received. The ledger can be queried and searched, and it provides metrics against the underlying trades so your application can inspect historical activity and build reporting workflows without standing up a separate event store and analytics pipeline first.

​

Controls

Anthid includes multiple layers of safety guardrails and controls that can be used to shape when trading is allowed. You get a practical risk control layer without having to build the entire control platform from scratch. Organization-wide circuit breakers can enable or disable trading across the organization. Account-specific controls can enable or disable trading for an individual linked broker account, including optional time windows that define when trading is allowed. Symbol-specific controls can also be configured to enable or disable trading for selected symbols, with time window controls available when more precise limits are needed.

​

What you can build

• Connect and manage broker accounts
• Submit trading intents through the API
• Track order and account updates as they happen
• Enforce organization, account, and symbol-level controls
• Serve hundreds of client connections through managed broker connectivity
• Integrate Anthid into internal tools, dashboards, and automated workflows

​

Next steps