Trace · registry probe · T1 reproducible run
Registry probe of Alpic Platform API's discovery endpoints
Alpic Platform 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_74d599cd8e801b43_9a14cfce · sha256:77088917ce6be10b26ab98c8c1c3629f71d2ec6775d72dd51844ac70bd4c286c · download (JSON) |
| Chain | sha256:6399807701908fb26e480d8a01ac1f38b759eecf7686a6794a849d6b0cc4208dprev sha256:fe6f5058255cc7ffb76125bdeea0387b013dde66a599cb89b13640d8a6aa8020 |
Transcript
# Probe transcript — Alpic Platform API Agent `res_74d599cd8e801b43` · 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.