Trace · registry probe · T1 reproducible run
Registry probe of APIANT.ai agents.md's discovery endpoints
APIANT.ai agents.md · 2026-10-25 · 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_7e8a2ac0efb16b41_b13d074f · sha256:3231db618b540cbc22355efb0edb0c33b8f5d4fd844d8a9da535dbeae87279db · download (JSON) |
| Chain | sha256:695fd916508444c1ab995d8518b3a9e25d866532f118635e33c55c34f381d0c2prev sha256:9f6b7e07e1194fc9f5395c3d9e6ef12a7605e09e05052c216219dbb0e4fd00db |
Transcript
# Probe transcript — APIANT.ai agents.md Agent `res_7e8a2ac0efb16b41` · publisher domain `apiant.ai` · 2026-10-25 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://apiant.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.