What PacSpace works with
The write is one call from your own code, so it sits beside the model, the framework, the runtime and the cloud you already run. What your side needs, what your tools read, and what the other side needs to check.
PacSpace adds a record and replaces nothing. The party running the agent writes each entry from its own code, in the place it already logs what the agent did, and whoever relies on the record checks it without anything from you or from us. This page lists what each side needs.
Your side: the write
| What you run | How it writes to a record |
|---|---|
| TypeScript or JavaScript | @pacspace-io/sdk on npm, Node.js 20.19 or later. See TypeScript. |
| Python | pacspace-sdk on PyPI, Python 3.10 or later. See Python. |
| Any other language | The HTTP API: one POST per entry, with your key in x-api-key. See Write an entry. |
| Your agent harness or framework | The write goes where your code already logs an action: the harness, the tool router, the job runner. The agent never holds the key. See Where the write goes. |
| NVIDIA OpenShell | Each decision it logs in OCSF, the open security log format, allowed or blocked, becomes an entry, sent by the SDK's two lines. See NVIDIA OpenShell. |
| Any other log your code can read | Each event worth answering for becomes an entry that carries its fingerprint. See Integration patterns. |
The write works the same whichever model, framework or cloud runs the agent, because it comes from your code and not from the agent. PacSpace is not in the path of the action: the write reports something that has already happened, so the action doesn't depend on it.
Your tools: reading the record
What you build reads the same record the Shared Record and the checker read.
records.historyreturns every entry with its status and receipt. See History.- The
record.committedwebhook tells your system the moment an entry is committed. See Webhooks. records.checkruns the check from your own code. See Check.
The other side: checking
Nobody on the other side has to sign up, install anything, or agree to anything first. They just check it.
- The Shared Record. You share one link, and the check runs in the reader's own browser. See What the reader sees.
- The open-source checker. Anyone who holds the history file can run
npx @pacspace-io/check history.jsonon their own machine, with no account, no key, and no call to PacSpace. See Check.