Usage reports and audit

Every priced call is recorded against the user and the organisation. Reports turn that ledger into invoice preparation; audit rows show what each turn did.

Usage reports (staff)

Open the client's HSAI Agent tab, step 5 Paid billing, then Show paid billing settings. The Usage and invoice preparation area:

Choose a closed UTC window (start inclusive, end exclusive), or Through now, which includes today's calls up to the database time.
Select Prepare usage report.
Download the usage report JSON (the full snapshot with an observation time and SHA-256 digest) or the invoice preparation CSV.

The report contains organisation and per-user totals, original call IDs, token categories, the retained model, tariff and pricing versions, and held reservations. Provider cost appears only in the HSAI report.

When export is blocked

Pending, unknown, exception or unpriced Slack calls stay visible and block the invoice CSV. The report says to reconcile usage first.
Reports above 10,000 calls are refused. Use smaller windows.
A pricing mismatch refuses the report rather than exporting a guessed total.

Finance issues the actual invoice in its own system and keeps the report JSON, digest, window and invoice reference with it. The report is not an invoice or proof of payment.

Usage reports (customers)

Customer administrators see a Usage reports area only when HSAI has set a billing policy for them. It shows their own organisation only, without provider cost.

Audit rows

Each Slack turn writes, best effort:

One agent_turn row: intent summary, number of model calls, outcome, latency, the Slack user, team, channel and thread, the link and version IDs, and the IDs of its tool calls.
One tool_call row per call: tool name, arguments, result status, latency, linked to the MCP request ID.

The MCP layer records its own side of each call, so a Slack action can be traced through to the API. If an audit write fails, the loss is counted in telemetry.

Other records

Workspace connections: every bind and disconnect is an immutable event with who did it and the versions involved.
Seats, administrators, licences and funding: append-only, with who and when; staff changes are marked as staff.
Brief timeline: shows approvals and regenerations made from Slack.
Server logs: slack_event lines carry only IDs; slack_install_failed lines carry the same support reference the customer sees.