> ## 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.

# Introduction

> Build broker-connected trading workflows with Anthid

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 credential store, 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.

<Card title="Start with the quickstart" icon="rocket" href="/pages/intro/quickstart" horizontal>
  Create your first intent and start working with Anthid in minutes.
</Card>

## Platform Concept

Anthid sits between your application and a linked trading account. Your application sends a request to the platform, Anthid records the request, applies configured controls, routes it to the connected broker, and exposes broker updates back to your integration.

The result is a managed trading control plane: one place to connect trading accounts, accept actions, enforce guardrails, route broker traffic, stream updates, store activity, query historical records, and measure what happened. That is a lot of critical infrastructure you do not have to design, operate, and constantly patch yourself.

## Trading Accounts

Trading accounts are the primary boundary for broker-connected workflows. A trading account belongs to an organization, stores broker metadata, and is associated with encrypted broker credentials.

After an account is connected, connection status endpoints let you check whether the account is `Pending`, `Ok`, `Error`, or `Unknown`. These status checks are useful before submitting orders or when displaying broker health in dashboards.

## Intents

An intent is a request for the platform to perform an action against a linked trading account.

When an intent is accepted, it becomes the platform record of truth for the action Anthid agreed to relay. Intents support create, replace, and cancel commands, so applications can submit new orders and append later actions to the same intent lineage.

## Broker routing

After Anthid accepts an intent, the platform routes the order 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.

Broker responses are 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 updates are relayed back to your application through gRPC streaming as soon as they are received. This lets your integration react to order lifecycle events and position changes without waiting for polling.

Anthid also gives you more flexible client connectivity on top of broker limitations. Where a broker may expose limited streaming connections, Anthid can support downstream stream clients subject to your plan limits and multiplex updates through the managed broker connection.

## Ledger and Metrics

Orders and positions are stored in a ledger after they are received. Ledger endpoints expose latest state, historical records, and order stats so your application can inspect 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 and symbol-specific controls can be configured for manual restrictions, time windows, and risk limits. Applications can also call the evaluation endpoint directly to check the effective control state before taking action.

## What you can build

* Connect and manage trading accounts
* Submit trading intents through the API
* Track order and position updates as they happen
* Query current and historical orders, positions, and order stats
* Enforce organization, account, and symbol-level manual, time, and risk controls
* Serve downstream stream clients through managed broker connectivity
* Integrate Anthid into internal tools, dashboards, and automated workflows

## Next steps

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/pages/intro/quickstart">
    Create your first intent and learn the core workflow.
  </Card>

  <Card title="API Reference" icon="terminal" href="/api-reference/introduction">
    Review authentication, request formats, and endpoints.
  </Card>
</Columns>
