Attestation

Refused before it ran.

On 9 August 2026 at 21:45 UTC, a call to gpt-4o was evaluated against pii scan and was refused.

Issued at runtime by Seal. Signed so anyone can check it offline against the published public key. No prompt text, response text or customer name is included on this share.

Checking.

Running aqta-verify-receipt in your browser, against the published public key.

Authority: pii_scanbuiltin.pii_scan.v1
Signed: 9 Aug 2026, 21:45:39 UTC · 62 days ago · key 9Y3Eiq6V…YFdvWa4

All signed fields and the raw JSON

attestation_id: da6d73e3-3b9d-4e1e-8cb3-0f5552be9cc4
trace_id: 64c0ba7d-9d89-4f57-af92-7c91a35758df
model: gpt-4o
outcome: BLOCKED
policy_applied: pii_scan
request_hash: 1427c4baea714d8e8c826f11209c406eab4594669dc4e51de21831e57b4b09dd
cost_prevented_eur: EUR 0.0000
timestamp: 2026-08-09T21:45:39.448573+00:00
signature: VXJEV7WLtnYoyZXWHN…RHitsEBzBg
public_key: 9Y3Eiq6V8QjRDUM5nP…agfYFdvWa4

Model identifier attests the API endpoint called. Weight-level pinning requires provider-side attestation; Seal does not claim exact model weights behind a stable API name.

{
  "v": 1,
  "attestation_id": "da6d73e3-3b9d-4e1e-8cb3-0f5552be9cc4",
  "trace_id": "64c0ba7d-9d89-4f57-af92-7c91a35758df",
  "org_id": "6dfbf85a-1dad-4937-b6be-1b4ed7670e99",
  "request_hash": "1427c4baea714d8e8c826f11209c406eab4594669dc4e51de21831e57b4b09dd",
  "model": "gpt-4o",
  "outcome": "BLOCKED",
  "policy_applied": [
    "pii_scan"
  ],
  "cost_prevented_eur": 0,
  "timestamp": "2026-08-09T21:45:39.448573+00:00",
  "public_key": "9Y3Eiq6V8QjRDUM5nPqSwKIOPQaoEU4SbagfYFdvWa4",
  "signature": "VXJEV7WLtnYoyZXWHNGMKtPu-vejZIMhfrKiU3i7smjOvguj8Onw4PesSxcPq-x-h0msJKCQfPFqRHitsEBzBg"
}

Counsel loop

Would you attach this receipt to a memo, filing pack, or opposing-party exhibit, given a counterparty can check it offline against a published key? If not, refuse with a precise hole.

Preview attach pack

Cover note · attestation da6d73e3… · outcome BLOCKED
Receipt JSON (ATTESTATION-v1) for offline check
Verifying key pin · aqta-att-01269bb4b6a7d950 · 9Y3Eiq6V…
Verify URL · app.aqta.ai/r/da6d73e3-3b9d-4e1e-8cb3-0f5552be9cc4
CLI · npx aqta-verify-receipt receipt.json --key <pinned>
Rules in force + countersignatures when the session zip is available

Countersign and the attach pack need a signed-in account. Refuse works without one.

Attach pack includes rules in force (with policy versions) and any countersignatures. Seal attests what was decided and who cleared it, not that the decision was correct. Evidence for audit and regulatory review; not a certification, and not a claim that a court must accept it.

Verify locally

Save this receipt as JSON, then run one command. Flip any signed field and the check fails. Do not trust this page alone.

npx aqta-verify-receipt receipt.json --key 9Y3Eiq6V8QjRDUM5nPqSwKIOPQaoEU4SbagfYFdvWa4

the original verifies. an edited copy fails

Python: pip install aqta-verify-receipt
Node: npm install aqta-verify-receipt