Live demo
A record made by the same pipeline yours would use.
No signup and no sales call. Every value on this page comes from a record our production system signed and published. Read it, search it, then verify it without trusting anything this page tells you.
What you are looking at
An agent of ours, run on a schedule against a real task. The model chooses which tool to call and the call is really made, so the steps below are what happened rather than a script. The workload is ours and holds no customer data. The pipeline is the production one: the same collector, the same signing key, the same transparency log.
Five
What this proves, and what it does not
The narrow claim is the one worth making. Anything broader would not survive a security review, and you should discount any vendor who makes it.
It proves
- The record has not changed by a single byte since it was signed.
- It was signed by the key published at the link above, and you can check that key independently.
- It existed by the time it was committed to a public log that we do not control.
- The collector observed these models, tools, hosts, files and counts during the run.
It does not prove
- That the agent did nothing else. A record covers what the collector saw. Someone who removes the collector produces no record at all, which is why a protected resource can be configured to refuse any request that arrives without a valid attestation.
- That the work was correct or wise. This is evidence, not judgment.
- That the check in your browser is independent. This page is served by us. That is exactly why the verifier is open source and the same check runs from your own machine, offline.
- Anything about the future. An offline check uses the trust material you already hold, so while you are disconnected it cannot see a newer log checkpoint or a key revoked after you downloaded it.
Run this against your own agents
One command wires the collector into a Node project. Your prompts and data never leave your infrastructure.