A record of what your agents did, committed where no one can change it
The Records API commits each consequential action outside your systems as it happens. Anyone you choose can check it, without an account and without seeing inside.
- WHAT YOU ADD
- Two lines where you already log
- WHAT WE RECEIVE
- A fingerprint, never the contents
- WHO HOLDS THE KEYS
- You do
- WHO CAN CHECK
- Anyone with the link, no account
- IF PACSPACE IS GONE
- An export still checks
How the record gets made
Your system writes the record. Nobody who checks it has to sign up, install anything, or agree to anything first. They just check it.
- 01 · THE AGENTtakes an actionacts16:42:07 UTC
- 02 · YOUR SYSTEMwrites the recordcommits the entry
- 03 · THE PROOFwritten once, unchangeableheld where no one can change it, PacSpace included
- 04 · THE CHECKERanyone with the linkchecks against it, without askingANY TIME AFTER
FIG. 1 · Your own log can be checked against the proof too. Details are checked only if someone asks for them.
Two lines of code. That’s the integration.
Add them where your system already logs what an agent did. Nothing to host, and nothing in the agent’s path.
const { ref } = await fingerprint(output);
await pac.records.emit({
record: 'prod-db',
title: 'Deleted table',
occurredAt,
actorId: 'agent-412',
payloads: [ref],
});
ref = fingerprint(output).ref
pac.records.emit(
record="prod-db",
title="Deleted table",
occurred_at=occurred_at,
actor_id="agent-412",
payloads=[ref],
)
- 1fingerprint() runs in your process.The contents of what the agent did never leave your system.
- 2records.emit commits the entry.The fingerprint and the entry’s fields go to PacSpace, where no one can change them, PacSpace included.
The answers your security review will ask for
The record is only worth what it survives. Here is what PacSpace sees, what it doesn’t, and what happens when something goes wrong.
- What leaves our environment?
- A fingerprint of each entry and the entry’s fields. fingerprint() runs in your process, so the contents never leave your system.
- Who holds the keys?
- You do. Your code signs each entry with your key, and encrypts it with a secret only you keep. Encryption is on by default: set the secret once, and it’s on. PacSpace never receives it.
- Can anyone change a committed entry?
- No one can, PacSpace included. A changed, missing or reordered entry shows when it’s checked.
- What happens if PacSpace is unreachable?
- Recording runs beside the agent, not in its path. Your agent keeps working, and entries commit when the service returns. Nothing weaker is ever written: an entry that can’t commit in full is reported as not committed, and sending it again is safe.
- What if PacSpace is gone?
- An export still checks. The open-source checker runs on your machine and never calls PacSpace. It reads the proof layer to check each entry, and with --offline it checks the file alone, with no network at all.
- Is the receipt proprietary?
- No. Each commit returns a standard transparency receipt that any SCITT checker reads.
- Where does it run?
- In our cloud by default. For closed and air-gapped networks, we work out the deployment with you.
Anyone you answer to can check it. Nobody has to trust you, or us.
Two ways to check a record, both built on the Records API. Neither needs an account, and the checker doesn’t need PacSpace at all.
$ npm i @pacspace-io/check $ pacspace-check ./prod-db-export.json 18,240 entries checked Unchanged, in order, nothing removed.
PacSpace commits the record. You build on it.
The Shared Record is one tool on the Records API. Yours can be another.
pac.records.history({ record })pac.records.check({ history })npm i @pacspace-io/checkWhen an agent acting for you does something you have to answer for
There is a record, not an argument. Whether you sell agents or run them, the people who rely on them can check what happened.
Check what an AI agent did for a program, without taking anyone’s word for it
Oversight checks the record, not the contractor’s report, and nothing inside has to be handed over to do it.
Tell us what your agents do.
And who has to rely on what they did. We’ll show you the record for an action like theirs.
U.S. Patent No. 12,682,346. Additional patents pending