Insights shows credit consumption by source, member, workspace, and model, alongside retained workflow and Chat activity. Use it to find spending drivers, investigate workflow performance, and export credit events for reporting.
Organization owners and admins open Settings → Organization → Insights. Regular members cannot view organization usage, including their own contribution. Billing-enabled deployments require Enterprise; billing-disabled deployments use the feature configuration under Self-hosted setup.
Choose a period
The period applies to every tab's charts and breakdowns. The Usage heatmap below the credit chart in Overview and workspace details always shows the last 365 days, including today's partial day. Hover, select, or use the arrow keys to inspect a day. A positive charge below one displayed credit reads <1 credit and remains colored.
Daily bars and heatmap cells use your browser's timezone, while billing periods begin at a fixed UTC instant. The first and last bars can be partial. Different timezones can split the same total differently across days.
Spend is in credits, where 1 credit = $0.005; the UI rounds displayed credits. Logs and Logs API costs are in USD, while Billing and run-resource API amounts use their documented credit units. Check the endpoint contract before comparing amounts. See cost calculation.
Read the tabs
A workspace detail splits usage into Sources and Workflows. Sources covers all attributed credits; Workflows covers only the workflow-run ledger. For example, 4,274 Chat credits plus 161 Workflow credits totals 4,435, while the workflow list accounts for 161. Open logs, where available, opens audit logs filtered to that workspace.
Activity and performance
In Activity, group by Workspaces, Workflows, Members, or Triggers. Sort by run volume, failure count, or average workflow duration. Members rank recorded Chat runs. Pages limit visible rows; totals and sorting cover the whole selected period. Select a workspace to narrow results and use All workspaces to clear it.
These metrics follow retained history and current workspace/organization ownership. Deletion or moving a workspace can change historical totals. Outcome and duration reflect the latest recorded state even when a run started earlier. Activity does not read Chat transcripts or workflow trace payloads.
Credits come from a separate billing ledger, so activity counts need not match credit-event counts. The credit export does not export activity. This view does not provide exact per-chat cost, connector/skill adoption, or attribution of generated artifacts.
Credit sources
Each charge has one source. The exact Agent block label in Insights refers to the Sim Chat workflow block (mothership_block), rather than the ordinary Agent block.
An ordinary Agent block's hosted model calls remain under Workflow. The Workflow base charge applies even without model calls. To assess a workflow using the Sim Chat block, read its Workflow charges and the separately metered Agent block source; neither charge is counted twice.
A hosted-key tool called inside a workflow belongs to Workflow; the same tool called directly belongs to API tool call. Chat panel, API agent, and Inbox charges cannot be separated by source. Dedicated workspace attribution can distinguish them when those surfaces actually name different workspaces. Usage without a workspace link appears under Unassigned usage and remains part of the organization total. This includes organization-level activity and retained charges from permanently deleted workspaces; the row cannot distinguish between them.
Reconcile totals
Members, Workspaces, and Sources are separate groupings of the same ledger. Each covers the period's charges; adding groupings together double-counts. Rounding can obscure small differences.
Models covers model charges only. Base charges, hosted tools, and fixed charges explain why it can be lower than the total. The current billing period lets you compare consumption with Billing; rolling windows do not align with invoices, and consumption is not a complete invoice including other fees or taxes.
Bring your own keys
A workflow model call using a workspace or organization provider key has zero model credits while its token usage is still recorded. Those tokens are not broken out in the Insights panel's credit totals. This statement describes verified workflow-model recording; other own-key surfaces do not have an equivalent breakdown here.
BYOK does not remove the workflow base charge or separate hosted-tool and sandbox charges. Confirm which key was used when investigating an expected zero-cost model call.
Export credit events
Click Export for the selected period and filters, or All events for the individual ledger entries and their filters. CSV columns are Date, Source, Description, Workflow, Credits; credits are numeric with four decimal places and can be summed.
Exports stop at 100,000 events. A truncated export still downloads and shows a notice; narrow the date range and export the remaining periods. Fractional CSV values can differ from whole-credit UI rounding.
For automation, use the organization usage summary, breakdown, and events APIs. Billing CLI account reads are a separate view from this organization report.
Self-hosted setup
Enable Insights through enterprise configuration or explicitly set:
Explicit values take precedence over the enterprise master configuration. Billing-enabled deployments retain the Enterprise gate. Organization owner/admin access is still required. See self-hosted enterprise setup.