Usage & Limits

What your account is consuming and where the ceilings are.

GET/account

One endpoint for the whole account picture: identity, plan, entitlements, and live consumption against them — an agent needs a single small read to know where it stands.

Response — 200

{
  "id": "acct_01j8xq2v9…",
  "email": "operator@example.com",
  "plan": "free",
  "created_at": "2026-07-28T09:12:00Z",
  "limits": {
    "active_deployments": 3,
    "concurrent_backtests": 2,
    "requests_per_day": 10000,
    "api_keys": 10
  },
  "usage": {
    "period": "2026-07-28",
    "requests": { "used": 1893, "limit": 10000 },
    "deployments": { "active": 2, "limit": 3 },
    "backtests": { "running": 0, "limit": 2 },
    "by_key": [
      { "key_id": "key_01j8xq2v9…", "requests": 1240 },
      { "key_id": "key_01j8xr8m1…", "requests": 653 }
    ]
  }
}

usage.period is the current UTC day; what counts against budget is defined with the limits.

Plans & pricing

The Free tier is real, not a trial: 3 deployments, full API access, paper trading, backtests — enough to run a small live desk at $0. Pro pricing is set at launch and will be published here first; there are no per-request or per-deployment-hour charges in either tier at launch. (These entitlement numbers are the design target and are being confirmed against current account tiers — tracked in the design log.)

Plan changes happen at account.superior.trade; the API reflects them immediately. The usage object is deliberately shaped so meters can be added later without breaking readers.