Usage, costs, and activity details
Steinkauz shows usage and costs for your active context across web chat and API Access in one place. Switch in the organization switcher to see a different workspace’s usage.
Where to find it
Open Usage & Activity from the main navigation. The page has three tabs:
| Tab | What it shows |
|---|---|
| Cost | Spend over time, remaining budget on Gateway plans, breakdowns by model or provider, plus Gateway web search spend and billable call counts |
| Inference | Searchable log of model activity from chat and API requests |
| Tools | Tool calls from chat or API completions (name, Tool backend when recorded, status, timing, attributed cost when known) |
Filter by date range and, on the Inference tab, by source (Chat or API), model, API key, provider, and trigger type.
In organizations, owners and admins can also filter by member (Myself, All members, or a specific person) to audit costs and inference across the organization. Admins see metadata only for other members (costs, tokens, models, timing — not titles, prompts, or message content). Owners can open full activity details including prompts/snapshots and Open chat for audit. Members always see their own usage.
Active context
Usage, budgets, and billing actions always reflect your active context:
- Personal (Individual) — your individual subscription and Budgets
- Organization — the organization’s subscription; on Gateway plans, Budgets allocated from the System Gateway pool (Settings → Budgets)
Organization owners see Manage billing for the active organization from this page. Only owners can open the billing portal for an organization. See Organization billing & seats.
Chat and API in one view
Web chat and API Access share the same activity log for the active context. Each row is one user-facing request. Source badges distinguish Chat from API (with API key label when applicable).
Gateway plans
- Individual (Personal): Chat and API draw from your System Gateway Budgets for Personal context.
- Organization: Chat and API draw from each Budget subject’s caps on each provider instance. Org Gateway money comes from the System Gateway pool admins allocate in Settings → Budgets (not independent non-pooled seat grants).
When Remaining reaches zero for a configured Budget unit, new requests for that subject on that provider are blocked until renewal or you raise the cap. See Usage Budgets.
BYOK plans
Steinkauz does not bill inference. Usage is still recorded so you can reconcile with provider accounts. BYOK stays uncapped by Steinkauz until you set optional Budgets. A billable seat is still required to use chat and API in an organization.
What you can inspect
Click any row in the Inference or Tools tab for activity details:
- Model and provider per step
- Tokens and cost per step and for the full request
- When Gateway web search ran on a step: inference vs web-search cost split and billable search call count
- Duration and time to first token
- Tool calls — which Tool backend ran (kind, attachment mode, backing provider/model, Environment class at call time), inputs, outputs, approval outcome, and attributed cost when known (owners; own data for everyone)
- Message context and JSON export (owners for other members’ rows; always for your own)
Multi-step requests (e.g. tool call then continuation) appear as one entry with multiple steps.
Activity details in chat
- Session activity — Chat top bar → activity panel for the current conversation; link to Usage & Activity filtered to that session.
- Message activity — Activity button on assistant replies for that response’s details.
Cost and budget summary
| Plan type | Individual (Personal) | Organization (Gateway) |
|---|---|---|
| Budget | System Gateway pool / caps in Settings → Budgets | System Gateway pool allocated across members + API allocation |
| Exhausted | Block chat/API when Remaining ≤ 0 for that subject × provider | Same Budgets rules per subject × provider instance |
| BYOK | Uncapped until optional Budgets are set | Same; billable seat still required |
For plan details, see Plans overview and Audit logs for policy change history.