Trace · registry probe · T1 reproducible run
Registry probe of Aard REST API's discovery endpoints
Aard REST API · 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
| Entry | GET on the publisher's well-known discovery paths |
| Actions | served Agentic Resource Discovery (ARD) document |
| Egress | no |
| Human approval | — |
| Secrets touched | no |
| Bundle | bundles/tr_st_d19afe7dd1d840aa_85c526c1 · sha256:7f22425ba8a6ff7005b650c82a81fdfe988eb19b4922152f428bc2521ff65726 · download (JSON) |
| Chain | sha256:35723530bff3d570a3daf348685f24f3fb5bc51f518c737b2126570e05e9aa75prev sha256:c0fb443187cf612f84fe90e8618a9cf970aee7d77a63e744fae2f05cb533e21a |
Transcript
# Probe transcript — Aard REST API Agent `res_d19afe7dd1d840aa` · 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.