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.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Trace · registry probe · T1 reproducible run

Registry probe of Aard llms.txt's discovery endpoints

Aard llms.txt · 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. ARD verified

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_157b48ec195d47b4_e926164c · sha256:6a92215c3601e92b20a33162eb12bffe6818ca9a3e2c53f53619959f0af6ffd4 · download (JSON)
Chainsha256:a94803edc09adb25a8af61c46173e0c5bbbaab71f560c4dcf8f66b6a9971a149
prev sha256:6042cb63ca2cc140acbf20c258a663a0155566eae0699f617a4d6f34e1d36064

Transcript

# Probe transcript — Aard llms.txt

Agent `res_157b48ec195d47b4` · publisher domain `aard.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://aard.ai/.well-known/ard.json`
- result: **verified**

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