Skip to content

Reports

What you'll learn: How to generate compliance audit reports from the Kyvvu platform.

Audit reports

The platform generates audit reports that summarize agent activity, policy compliance, and incident history. Reports are available in PDF and XML formats.

Generating a report

Via the dashboard

  1. Open Workspace → Reports.
  2. Select the report parameters:
  3. Start date and End date - both required, both inclusive.
  4. Format — PDF or XML.
  5. Sections - tick which of agents, logs, incidents and events to include.
  6. Click Generate.
  7. Download the report when ready.

There is no per-agent filter: a report covers the whole workspace for the period.

Via the API

curl "https://platform.kyvvu.com/api/v1/reports/audit?format=pdf&start_date=2026-04-01&end_date=2026-04-30" \
  -H "Authorization: Bearer <JWT>" \
  -o audit-report.pdf

Query parameters:

Parameter Type Required Description
start_date YYYY-MM-DD Yes Start of the reporting period, from 00:00:00.
end_date YYYY-MM-DD Yes End of the reporting period, to 23:59:59.
format pdf or xml No Output format. Default pdf.
environment string No Restrict agents, logs and incidents to one deployment environment.
include_agents, include_logs, include_incidents, include_events boolean No Include that section. Default true for each.

Report contents

Reports include: - Summary - counts of agents, tasks, logs, incidents and events; active incidents; and how many tasks have a valid or an invalid hash chain. - Agents - agents active in the period, with their classifications and environments (the PDF lists the first 50). - Logs - task executions with the status of each task's hash chain (the PDF lists the first 100). The chain (v1) is computed by the client and verified by the platform when it ingests the trace, or computed by the platform for a client that sent no hashes. "Valid" means the stored entries agree with the hashes the platform recomputes from them; it does not cover kind, verb, timestamp, output or properties, and it is not proof against anyone with write access to the platform's database. The PDF prints this caveat under the table, and the XML marks each task with <chain_version>v1</chain_version>. - Incidents - policy violations in the period (the PDF lists the first 50). - Events - the most recent 100 platform events (user actions).

XML reports use a structured schema suitable for automated compliance tooling and regulatory submission.

Next steps