Usage and request evidence

Open Activity from the main navigation.

Members start with their cost overview and remaining budgets. Owners/admins start with requests and can filter team usage. Access is limited to your organization and role.

Statistics

Cost and token tabs show recorded consumption over the selected period. Remaining budgets reflect the current period and active caps. A missing optional cap is not a balance of zero; other applicable limits still matter. Recorded cost is not a replacement for your provider’s invoice.

Request detail

The Requests tab lists allowed and denied routing decisions in a searchable table. Filter by date, member, model, API key, connection, outcome or processing status. Sort by time, model, member, key, connection, outcome, status, recorded cost, tokens or decision ID. Open a request to see who made it, the selected model and connection, declared and effective sensitivity, environment, policy outcome, usage, cost and budget attribution.

Decision, generation, turn and session identifiers connect records. Correlations remain available after transcript content expires. Safe file evidence distinguishes observed metadata from client assertions and never offers original file downloads.

Tool invocations are client-reported call/result evidence. They do not prove that Steinkauz executed, approved or governed an external action.

Inputs, outputs and metadata

Request detail shows a read-only conversation log. System/developer instructions can be expanded; submitted assistant history is labeled as input and generated messages as output. Tool calls and results are shown as reported evidence.

Expand request and response data for generation parameters, conversation context and structured payloads such as embedding inputs/vectors. Request evidence includes allowed and policy-denied requests. Chat Completions and Responses retain output content; evidence for streamed requests shows the completed output. Responses retain audit evidence even when store=false; that flag controls Responses retrieval and continuation. Authorization headers and cookies are never copied.

Members can inspect their own content. Owners can inspect tenant content; admins can inspect team metadata but cannot read other members’ content. The same controls apply to the download.

Content retention defaults to 30 days; your deployment’s configured period may differ. Request detail shows the expiry time. Expired, erased or unavailable historical content cannot be retrieved, while policy and usage records remain. File bodies, base64 and recoverable attachment URLs remain omitted.

Download evidence exports the permitted content and metadata as JSON (schema version 2). Organization-wide archival export is an operator workflow. Configuration history shows control changes separately.