Skip to main content
Your organization’s billing claims describe its feature access and usage limits. Read the resolved claims instead of hardcoding values from a pricing example: plans and organization overrides can change them.
Users and API keys can read their own organization. Service tokens require billing:read. A missing billing identity returns 404; an unauthorized organization lookup returns 403.

​
Entitlements and permissions

The response has entitlements and limits. Entitlements describe plan access, including tier, controls, trading, and support. Permissions separately determine what the credential may do. Having a live-trading entitlement does not grant intent edit permission. Paper and live use the same intent API, but live creates require live-trading access. Account controls are available on live plans; organization and symbol controls require premium controls access. See Controls for the checks on each scope.

​
Usage limits

A platform request limit is separate from a broker’s rate limit or supported order capabilities. Raising your Anthid allowance does not raise the broker’s allowance. A rate-limited REST request can return 429; pace requests and avoid blindly retrying order submissions. See Request correlation and retries.

​
Retention is separate from query access

Stream snapshots follow a separate policy: terminal orders and zero-quantity positions expire after one hour. Working orders and nonzero positions remain until updated. This affects priming and reconnects, not the ledger’s history. See Streaming delivery. Order, position, and archived intent records have six-year storage retention. This does not grant every plan a six-year API query window. Ledger history requests are bounded by the caller’s retention_days, and analytics also have endpoint-specific limits such as the 1 to 90 day window. See Ledger.