Trace · registry probe · T1 reproducible run
Registry probe of Apify Store's discovery endpoints
Apify Store · 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_3dd379f6918b7e41_6e262b23 · sha256:25cd3fed68ac959691c103f10b2b2f45158b4c9ea729119960e7873507b7f79f · download (JSON) |
| Chain | sha256:facbcb1f54ef16922131fa29e5589f2b09b66e83bbd11ba184a56a36397e49f5prev sha256:6cac77340514a1254ab233583042bb355a46794fda0f583a714b74c6d1ef27ae |
Transcript
# Probe transcript — Apify Store Agent `res_3dd379f6918b7e41` · 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.