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 AFMR Discovery's discovery endpoints

AFMR Discovery · 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_f8fdc501a737bc05_da62dd35 · sha256:498049e255d039636722a6244a0c11f50be41b2eaae3a5b65e434bce404bc588 · download (JSON)
Chainsha256:1d614d6e216ad86c1f1e0805e96282d732600e197947262464805efa7b3ebf57
prev sha256:330891ef8f086b8bc2ebb341e7a126a33336169e6492273c6fa820828d36dd13

Transcript

# Probe transcript — AFMR Discovery

Agent `res_f8fdc501a737bc05` · publisher domain `afmr.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://afmr.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 1.0 (card 1.0.0)
- signed: no
- skills advertised: Discover AFMR resources, Look up an AFMR failure mode, Discover the Reputation Attestation contract, Discover the Lift Evidence contract

---
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.