Trace · registry probe · T1 reproducible run
Registry probe of Annsa API's discovery endpoints
Annsa API · 2026-10-19 · 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_241c2df7ff3b78b7_50bd8651 · sha256:4d2c5fb5f18779f19e7725f721787c0fd2bc4d32edac140372a3fb605857f0e0 · download (JSON) |
| Chain | sha256:f841594e2e9d405bb8771e5db865c44bb0871f9c054c2d8fcda978b454be54d3prev sha256:4b0aba1a410eb9351280dfe58a67e966e459d5ea960883a5236ae219027e5e70 |
Transcript
# Probe transcript — Annsa API Agent `res_241c2df7ff3b78b7` · publisher domain `annsa.ai` · 2026-10-19 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://annsa.ai/.well-known/ai-catalog.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.