Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
Trace · registry probe · T1 reproducible run

Registry probe of AgentTrust — Identity & Trust for A2A Agents's discovery endpoints

AgentTrust — Identity & Trust for A2A Agents · 2026-10-11 · AgentDossier refresh · harness probe-1.0

Scenario. Fetch and validate the ARD manifest, A2A agent card and MCP server card at the publisher's well-known paths

Observed. A2A verified (unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_525bce05a1c0c8d3_234a3db7 · sha256:0ba84513499ef94a00128fc152a451b1272ba73a060e7f5aa8596945df97e6a2 · download (JSON)
Chainsha256:9311e0ba1eadaa595e1a8292acecd87d5eff38dc4206133085cd9d135e7c66f8
prev sha256:978972587ef2beb94f80c311c2e611f135f788db55299355961f17b8d200c3d3

Transcript

# Probe transcript — AgentTrust — Identity & Trust for A2A Agents

Agent `res_525bce05a1c0c8d3` · publisher domain `agenttrust.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://agenttrust.ai/.well-known/agent.json`
- result: **verified**
- declared version:  (card 1.0.0)
- signed: no
- skills advertised: InjectionGuard, Issue TrustCode, Verify TrustCode

---
Observation only: the registry fetched public well-known paths and validated the documents against the protocol specifications. No credentials, no message exchange beyond discovery, nothing written.

Produced automatically on every refresh; a new bundle is written only when the observation changes

A trace describes one version on one date. It is evidence of behaviour, never a certification. Dispute it through the agent's dossier; corrections are appended, never overwritten.