THE RECORDS API · FOR SECURITY, RISK AND COMPLIANCE LEADERS

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 IT WORKS

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.

  1. 01 · THE AGENTtakes an actionacts16:42:07 UTC
  2. 02 · YOUR SYSTEMwrites the recordcommits the entry
  3. 03 · THE PROOFwritten once, unchangeableheld where no one can change it, PacSpace included
  4. 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.

INTEGRATION

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],
});
  1. 1fingerprint() runs in your process.The contents of what the agent did never leave your system.
  2. 2records.emit commits the entry.The fingerprint and the entry’s fields go to PacSpace, where no one can change them, PacSpace included.
AIR-GAPPED NETWORKS Running agents on a closed network? Tell us about your environment, and we’ll work out the deployment with you. Let’s chat
SECURITY REVIEW

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.

DATA
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.
KEYS
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.
INTEGRITY
Can anyone change a committed entry?
No one can, PacSpace included. A changed, missing or reordered entry shows when it’s checked.
AVAILABILITY
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.
EXIT
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.
STANDARDS
Is the receipt proprietary?
No. Each commit returns a standard transparency receipt that any SCITT checker reads.
DEPLOYMENT
Where does it run?
In our cloud by default. For closed and air-gapped networks, we work out the deployment with you.
CHECKING

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.

THE SHARED RECORD One link, opened in a browser For the people you answer to: an auditor, counsel, an insurer, a program office. They open the link and check it, with no call to you.
SHARED RECORD · PROD-DB TRAILREAD ONLY
18,23816:40:12Unchanged
18,23916:41:55Unchanged
18,24016:42:07Unchanged
Checked in your browser. Details stay sealed until the operator shows them.
THE OPEN-SOURCE CHECKER An export, checked on your machine For a reviewer who checks all day, or an auditor who checks once. It runs on their machine or in their pipeline, and it survives the company.
CHECKER · ON YOUR MACHINENO CALL TO PACSPACE
$ npm i @pacspace-io/check
$ pacspace-check ./prod-db-export.json
18,240 entries checked
Unchanged, in order, nothing removed.
The open-source checker
UNCHANGEDThe entry matches its proof, held where no one can change it, PacSpace included.
COMPLETEIn order, nothing removed. A missing or reordered entry shows.
MATCHESWhen the details are handed over, they’re checked against the seal.
BUILD ON IT

PacSpace commits the record. You build on it.

The Shared Record is one tool on the Records API. Yours can be another.

READYour own viewsRead a record’s history into your dashboards, reports or review tools.pac.records.history({ record })
CHECKYour own checksRun the same check in your process, on your schedule, from outside the room.pac.records.check({ history })
EXPORTWithout PacSpaceThe open-source checker reads your workspace export, so records can be checked without us.npm i @pacspace-io/check
FOR ENTERPRISE

When 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.

An agent deletes a production database.The record shows the action, when it was committed, and that nothing has changed since. Counsel sends a link, not a log export.
An agent changes who can see customer data.The access change is on the record before anyone asks. An auditor checks it without opening your systems.
An agent closes a customer’s case.The customer, or their advocate, can check what the agent did, without taking your word for it.
FOR GOVERNMENT

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.

A contractor’s agent processes benefit claims.Each decision is on the record as it is made. The program office checks the record, not the contractor’s report.
An agent works through case files.Oversight sees what was opened and changed, in order, with nothing removed.
A program changes contractors.A record committed under one contract is checkable after the contract ends.
OREGON EXECUTIVE ORDER 26-26 · 23 SEPTEMBER 2026 Oregon now makes it state policy to buy frontier AI that has received independent third-party review, and asks for transparency and accountability in how the state uses 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