Skip to main content

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 is designed around a simple integration model: use the REST API for submissions and queries, and use the gRPC stream for live execution context as broker activity happens. This gives your application a clean split between command/query workflows and real-time updates. You can submit intents, query accounts, search ledger activity, and inspect platform records over REST, while a connected gRPC client receives immediate broker responses and execution updates.

​
REST API

Use the REST API for request/response workflows. REST is the right path for submitting intents, querying platform resources, reading ledger records, and building dashboards or internal tools that need durable platform state. REST requests and responses use JSON. 
curl https://api.anthid.com/v1/intent \
  -X POST \
  -H "x-api-key: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "YOUR_ACCOUNT_ID"
  }'

​
gRPC streaming

Use the gRPC stream for live context and execution updates. As Anthid receives responses from the connected broker, updates are relayed to your gRPC client as soon as they are available. This gives your application immediate context around accepted orders, rejected orders, fills, and other execution events without polling. 
grpcurl \
  -H "x-api-key: <YOUR_API_KEY>" \
  api.anthid.com:443 \
  list
1

Submit or query over REST

Send intents, search records, and query platform state through the REST API.
2

Listen over gRPC

Keep a gRPC stream connected for immediate broker responses and execution context.
3

Read historical state from the ledger

Use REST queries against stored ledger data for search, metrics, reporting, and reconciliation.

​
Why this model works

REST gives teams a familiar JSON interface for durable operations. gRPC streaming gives teams low-latency updates without building and maintaining a custom broker streaming layer. Together, they let your application send commands, observe execution, and query history through Anthid’s managed platform instead of stitching together separate broker clients, event streams, and storage systems yourself.