Fields, grouped
Thirteen fields in four groups, followed by what the record declares. The fields and views are defined in the draft specification. Agent type takes one value per AIAO dimension, with cognitive capabilities listed as properties.
Descriptions in italics (protocol, authority, policy) are proposals still open for discussion in the W3C AI KR Community Group.
Write a record
Fill in the form; the card on the right updates as you type. Add it to the register when done.
Agent trust register
The first row is an invented example to show the shape of a record. Delete it when adding your own.
The register is kept in this browser only. Copy the CSV or JSON to keep it elsewhere.
Mappings
Which agent identity and trust specifications have an element matching each field of the trust record. A first reading of the specifications listed in the Agent Trust Protocols and Specifications Explorer, checked 18 November 2026. Each project owner is invited to confirm or correct their row.
| Group | Trust record field | Specifications with a matching element |
|---|---|---|
| Identity | Name or identifier | ARIA (did:aria), ATP (did:atp), ANP (did:wba), MCP-I, NTI-1, APS, ODIS (agent package and runtime instance), WIMSE |
| Identity | Agent type | None of the specifications read. No specification types the agent by role, capability or embodiment; this is where AIAO adds to them. |
| Interface | Protocol | Implicit only: MCP-I and the China Mobile MCP draft bind to MCP; UCP is itself the protocol. |
| Interface | Where it lives | ARIA (DNS pointer to the Agent Identity Document), ATP (did:atp builds on did:wba: DNS and HTTPS resolution), ANP (web-based DID), Web Bot Auth (key directory URL) |
| Interface | Key publisher | Agent's own origin: Web Bot Auth, UCP, PAP, PACT. Issuer or network chosen by the verifier: KYAPay, Visa TAP, x402. Registry or domain: ARIA. |
| Mandate | Mandate / functions | AAE (MANDATE block), AMEP (the delegated mandate), RTTP (names the intended action), ARIA (scopes) |
| Mandate | Authority | ODIS (delegated authority), MCP-I (delegation), APS (authority narrowed at each hop), NTI-1 (capabilities), AuthZEN (authorization decisions), ATP (mandates, in draft) |
| Mandate | Policy | AAE (CONSTRAINTS block), NTI-1 (caveats: expiry, value, path limits), ARIA (ARIA AP admission), AuthZEN (decision) |
| Parties | Developer | None of the specifications read. |
| Parties | Deployer | ARIA (organisation that answers for the agent), ODIS (principal) |
| Parties | User | ODIS (delegated user identity), AMEP (the person who delegated), NTI-1 (principal-bound identity) |
| Parties | Owner, Funder | None of the specifications read. |
| Trust | Trust assertion | AAE (VALIDITY block), ATP (trust scoring and credentials, early draft), AMEP (each check returns preserved, violated or unresolved), IQA (whether attestation standing holds), ARIA (revocation status) |
Closest matches
ARIA touches the most fields: identifier, location, keys, scope, admission, accountable organisation and validity.
AAE mirrors the Mandate group: its MANDATE, CONSTRAINTS and VALIDITY blocks line up with Mandate, Policy and the trust assertion.
ODIS asks who the agent acts for, what authority it was given and which instance is acting, matching User, Authority and Identity.
AMEP tests whether an agent stayed within its mandate, the question the trust assertion asks, and adds a third outcome, unresolved, for missing evidence.
Where the record goes further
Agent type, Developer, Owner and Funder appear in none of the specifications read. These fields carry the AIKR and AIAO contribution.
Where the specifications go further
Delegation chains (AMEP, ODIS, APS), revocation and validity windows (ARIA, AAE), and evidence of what an agent did (AMEP, APS, NTI-1). Candidate additions to the record: a delegation chain and a lifecycle field.
This is an editorial reading. Rows for ODIS, MCP-I and the AuthZEN agent drafts rest on summaries of the specifications, not their full text. Project owners can submit a mapping profile for their protocol (field map with spec section references, an example record from their use case, and evidence level) as a pull request or issue on w3c-cg/aikr/trust, or by posting to public-aikr@w3.org with [trustvisualiser] in the subject.