For teams accountable for what AI is allowed to do.

Controls for AIthat hold when challenged.

A loan, a diagnosis, a claim. Cleared before it runs, signed when it happens, and checkable offline.

AI acts. Keep the receipt.

Check a receiptApply for a pilot

Why a seal

For three thousand years, when someone had to trust a thing they had not witnessed, we pressed a seal into it.

  • Who authorised this?
  • Has it changed since?
  • Can a stranger check it?

AI has learned to act. It deploys code, moves money, and writes to records that matter. The questions have not changed. The object has to. When the actor is an agent choosing its own tools, that gets its own record: ACTION-v1, decided before the tool runs.

Checking in your browser

Sample record, signed with the published demo key. A real production refusal is in the refusal ledger.

  "outcome": "BLOCKED",
  "model": "gpt-4o",
  "signature": "uZCP7STzFgHXbyIK1oKoZ5Zn8-…"

Authority can be delegated. Trust should remain checkable. Seal sits alongside the AI systems you already use and gives the teams running them a record they can carry into security review, audit and customer assurance.

Check a full record

Seal by Aqta

The next generation of "who cleared this?"

  1. Clear
  2. Seal
  3. Verify

Clear. Seal. Verify.

A loan, a diagnosis, a claim. Cleared before it runs, signed when it happens. Change one field and the check fails. Offline, without calling anyone. When a reviewer asks, the answer is a sealed pack they accept on the record. Built for the day someone challenges what your AI decided.

Try it: app.aqta.ai/verify

SealSample receipt
When
Before execution
Policy
Personal data check
Outcome
Allowed

Signing

Writing the signed record

Signed record

When the answer matters

Months later, someone asks what happened.

When a decision matters to someone outside your system, they need something they can check for themselves.

Without evidence that holds up, AI deployments stall in security review, procurement and audit. See a sealed record →

No regulation asks for cryptographic receipts. They ask whether your account of an AI decision stands up to scrutiny.

DORA, 2025Moffatt v Air CanadaFINMA 08/2024The full picture →

  • One pack, one link
  • Nothing to install
  • Still verifies years later
  • The verdict is signed too
docket · the record a review ends with

“Did this decision clear under the policy in force when it ran?”

evidence
receipt sealed · pack exported
signature
verified in the reviewer’s browser ✓
reviewer
no account · published key only
clock
question → sealed answer
✓ ACCEPTED · on the record

Our thesis

Receipts could do for AI what double-entry bookkeeping did for trade: a primitive small enough to deploy everywhere, large enough to change what cooperation is possible.

Read the manifesto

One Seal path

Seal one workflow. Keep the receipt.

Bring a loan, a claim or a clinical decision. We clear it to ship, and the record travels with it.

Checking a record is free and always will be. What a team pays for is making one at the moment the decision happens, and standing behind it afterwards.

  • Start where a person already signs off
  • Scoped engagement
  • Reply in 4-5 business days
  • Offline-verifiable trail
Seal pilotApply for a pilotOne named workflow.

Product notes by email