Trace · registry probe · T1 reproducible run
Registry probe of Alpic CLI's discovery endpoints
Alpic CLI · 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_a22ab255214603e3_a19b6a23 · sha256:52d5b309613a6f02462917e7c03de384ddec6d1de3f737e854c10dd5c7f6f0e5 · download (JSON) |
| Chain | sha256:68cfe9cf3c5ed72dfae501c89da025b752d688240684258143db41610a0a900eprev sha256:6406e9b1d9f2004ccec630cc65e0f6cbfdcffb6bf15c8921c4b0e7be092c9d52 |
Transcript
# Probe transcript — Alpic CLI Agent `res_a22ab255214603e3` · publisher domain `alpic.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://alpic.ai/.well-known/ai-catalog.json` - result: **verified** - warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search) --- 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.