Skip to content

Explain.

How every answer can be checked later.

Each call leaves a record: who asked, what they sent, which release answered and what it said. Records are sealed, so anyone can check that they haven’t changed.

When someone asks why a refund was refused, you can show them the record of that call. Every call is kept with everything needed to explain it, and sealed so a change to it would show.

Records can be followed across Decisions, and on paid plans exported or handed over as one evidence pack.

Who
Risk, compliance, support, or the customer who asks
Where
Audit in the app, MCP, or the CLI
You end up with
A sealed record of every answer

The record of a call.

Each call is recorded within seconds of its answer: the caller, the inputs, the release and revision, the model, the answers and their confidence.

  • The exact release and the Definition it came from
  • Answers and their confidence, as the model gave them
  • Inputs kept as your organisation chooses
  • Record before answering, if you turn it on, holds each answer until its record is kept

Sealed so it can be checked.

Records are sealed in batches, and each seal joins a chain where every entry is hashed over the one before. Anyone can check later that a record hasn’t changed.

  • typefuse audit verify checks the whole trail
  • Seals and root hashes are in every evidence pack, on paid plans
  • A changed record fails the check

Follow one request.

Calls that carry the same reference can be followed together, across every Decision a request touched.

  • One reference from your system
  • Every Decision it reached, in order
  • Each answer and the release that gave it

Who changed what.

Every change is on the trail too: who published, deployed or approved, and through which token or connected app.

  • People, deploy tokens and agents told apart
  • Approvals with the requester and the approver
  • Exported as CSV or JSON, on paid plans

One evidence pack.

For any Decision and period, download one zip: a PDF summary, every call and change, the evaluations, the seals and the Definition of each release involved.

  • A summary PDF a person can read
  • The raw files to check it against
  • On paid plans, the Founder trial included; the audit trail itself is on every plan

Where it happens.

In the app

  • Each call’s record from Activity or Audit
  • Audit: the trail and evidence packs
  • Exports as CSV or JSON, on paid plans

Your agent, over MCP

  • Reads a run and its release
  • Exports the audit for a period
  • Explains an answer from its record

Your code

  • typefuse audit verify
  • Exports for your own store
  • References you pass with each call

Private preview

Own your next decision.

Keep the judgement calls your agents and apps make under your control, with a record of every answer.

  • Your criteriaThe people who own a decision set its rules, and change them when the business changes.The people who own a decision set its rules.
  • Your evidenceEvery release is tested against real cases before your application ever sees it.Every release is tested on real cases first.
  • Your recordEvery answer is traced and sealed, ready for an auditor or the customer who asks why.Every answer is traced and sealed.