Weights · Agent · Actions · Evidence · Start pages

Get started

Each specification has its own start page. Pick the step in the chain your trust boundary needs; no step requires the others.

Python 3.11 or newer · Git and Bash on Linux, macOS or Windows with WSL · Software mode, no hardware isolation
The chain

Pick a step

01 · Weights Weight Custody Manifest

Install the reference SDK from source, sign a manifest as builder and custodian, verify it, and gate a key release. It runs on software test doubles, with no GPU or cloud account.

Getting started →

02 · Agent Agent Manifest

Sign a small agent configuration and verify its declared inputs, then watch an edited record and a changed prompt hash fail. It runs no model and produces no hardware attestation.

Create your first manifest →

03 · Actions cMCP

Run the runtime in dev mode, see a call to a sensitive tool get HTTP 403 before it is forwarded, and verify the signed TRACE claim. With no hardware TEE, verification reports partially_verified.

cMCP quickstart →

03 · Actions cA2A

Build a two-hop delegation chain and verify it, then see an untrusted root and a grant wider than its parent rejected. It needs no network, hardware or running peer.

Verify your first chain →

04 · Evidence TRACE

Sign a record, verify it, then change one field and watch verification fail. It uses synthetic claims and software signing, with no agent, registry or attestation.

TRACE quickstart →

04 · Evidence Conformance suite

Install agentrust-trace-tests, generate a Level 0 sample record, and run trace-tests verify against it. The sample passes Level 0; Levels 1 and 2 fail without attestation and anchoring.

Conformance quick start →

No install

Check real hardware evidence first

Verify a genuine Intel TDX quote from a GCP confidential VM in your browser, including its commitment to the key that signed a TRACE record. Nothing is uploaded.