How the record gets made.
With the PacSpace Records API, the company running an AI agent writes down each action as it happens, and anyone who relies on the agent can check it.
Four steps. One of them is yours.
An agent acts
An AI agent runs a step, takes an action, or produces a result on someone's instruction.
Not in the path of the action.
Your agents, your logs and your stack stay as they are.
The operator writes the record
The party running the agent writes what happened as the work happens, because it is the only party that can see it.
Committed before the question.
The record exists before anyone asks. The time it was committed is part of it.
PacSpace commits it
The record is committed where no one can change it, out of the agent's reach and out of your control after the fact.
No one can change the record, PacSpace included.
A correction is a new entry with its own stated reason, so the original and the change both stay visible.
Anyone who relies on it checks, without asking
An investigator, an auditor, a customer or an oversight body checks the record without asking permission, and checking never reveals what's inside.
The change shows.
A change to any copy shows at the next check. Checking does not require PacSpace to exist. The verification survives the company.
You write the record. Nobody on the other side has to sign up, install anything, or agree to anything first. They just check it.
Shared. Fixed. Private.
What each word means for whoever relies on the record.
It reads the same every time it is opened. Corrections are new entries with their own stated reasons, never edits.
Each entry is sealed and committed as the work happens, where no one can change it, PacSpace included. A change to any copy shows at the next check, and the record shows where. A correction keeps the original and the fix both visible. If writing stops, the gap shows: the records on either side put a start and an end on it.
Never published. The contents are shown beyond the two parties only by the record holder's deliberate, revocable choice.
What leaves PacSpace is each entry's seal. A seal shows that an entry was made and when, and nothing about what it says. You choose what each reader sees, and checking never shows a field you kept back. PacSpace holds what you write to run the service, encrypted in storage, and uses it for nothing else.
We make your AI agents' actions checkable.
Records API
Record what your AI agents do, as they do it. Keep the details private and prove what they did.
Also in Python: pip install pacspace-sdk
Read the quickstartconst { ref, blinding } = await fingerprint(output);
await pac.records.emit({ record: 'run-4417', actorId: 'agent-7',
title: 'Robot r-112 stopped', occurredAt: t, payloads: [ref] });Shared Record
Share a record with one link. The other side checks it without asking you, and sees only what you choose to show.
The checker
Check a record yourself with our open-source checker, with no account and without asking us.
An AI system leaves three trails.
You can test it again.
This trail is written down and reviewed before the system runs, often by many people.
Evaluations test the model before it runs. Each test run can be written as it happens, so the results come with a record of the run itself.
You can keep watching.
This trail is watched live by the party running it, so they can steer it as it goes.
Attestation shows where an agent ran and which code it ran. PacSpace adds a record of what the agent did, and anyone who relies on the agent can check it.
Guardrails decide what an agent may do. PacSpace doesn't decide anything. It commits the record of what the agent did and what its guardrails decided, so anyone who relies on the agent can check it.
You can't go back.
This trail is written as the work happens, and it's the one a customer, an auditor or an investigator has to rely on. Anyone who has to check the record is left with only the word of the party that produced it.
PacSpace commits it where no one can change it, PacSpace included.
Keep them. You hold the keys, so even when nothing changed, you can't prove it to anyone outside. The record is the part they can check. More in the FAQ
It is an integrity control on the record itself, and it composes with everything you already run; the perimeter protects where the record lives, we make what the record says checkable.
“We can replay the trace.”
A replay is read from a stored trace. That's the same record, in the same hands.
“We can rerun it with the same inputs.”
A rerun is a new event. It may not even do the same thing, and either way it isn't what happened.
“Nothing has gone wrong.”
Most flights go fine, and every one still carries a recorder. If something does go wrong, afterward there is a record, not an argument.
We do not judge, rank, meter, or score.
PacSpace records and never decides. It doesn't detect, prevent or stop anything, and it never says who is right. This is not about correctness. It is about transparency.
The record covers the actions you write, the same limit every log has. A gap in the record is as telling as a change: the records on either side put a start and an end on it.
Bring the case you think breaks it.
We would rather be evaluated by use than by description. Talk to us and we'll put you in a live environment: commit a record, do your best to change it, then check it yourself, with us out of the loop. The change shows.
The record must exist.