Trace · registry probe · T1 reproducible run
Registry probe of Apify agent quickstart (agents.md)'s discovery endpoints
Apify agent quickstart (agents.md) · 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_af51a0691826652e_26bb2220 · sha256:68483a521c4d5e027e643d7dfada315574924dd8798697f44fac7f384de51383 · download (JSON) |
| Chain | sha256:2b7bfc02f00dfe274912f5493e34fa8ccf05c520cabbcd506310253072861406prev sha256:0760111317e6b90f2dc7acd8966f805f1b8cbcc616a0820e154c89e504ac9503 |
Transcript
# Probe transcript — Apify agent quickstart (agents.md) Agent `res_af51a0691826652e` · publisher domain `apify.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://apify.com/.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.