Trace · registry probe · T1 reproducible run
Registry probe of AIvikings REST API's discovery endpoints
AIvikings REST 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_3d0b57233d90ee0f_2ccefa49 · sha256:f10bfe8071547e8cb40487c7994e3f473aad19d9184250dbcae4db0f2f8c4279 · download (JSON) |
| Chain | sha256:13ed6307b96ba3de66617e731c8483cf6475e71450c573b6b52b71d7a01c4d80prev sha256:ca5ce452d14cc9e88b75786c36ba365932e7fdaf29b78d63469e0a5a27855075 |
Transcript
# Probe transcript — AIvikings REST API Agent `res_3d0b57233d90ee0f` · publisher domain `aivikings.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://aivikings.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.