Trace · registry probe · T1 reproducible run
Registry probe of Events.Aero's discovery endpoints
Events.Aero · 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_d71e91ae43469852_4d73f575 · sha256:e60c65086439a369538c3566f1e84cb273ef64b9ecdea506fec286648091b136 · download (JSON) |
| Chain | sha256:4a631a84f694a73f4c050edd3931bf42389298fc005bca4e32c45f234882ddd2prev sha256:c8cc7a6aeb3a3bf51f56bdcb13dc01b95364768f5ce0b948a594dbef04c64151 |
Transcript
# Probe transcript — Events.Aero Agent `res_d71e91ae43469852` · publisher domain `events.aero` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://events.aero/.well-known/ai-catalog.json` - result: **verified** - manifest entries: 1 --- 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.