Trace · registry probe · T1 reproducible run
Registry probe of Apify Store search's discovery endpoints
Apify Store search · 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_4e2cee3879ebaa22_81a46edb · sha256:8eedbd7354bb67e137d8fba31d810cdfa723565edb561e430ca1b186c23c6770 · download (JSON) |
| Chain | sha256:ca31382a37d1010b0a9d9a5d4f47afc934bbdc9f24ee52be4ce0b71e26680e65prev sha256:45c37751f5452650f3281d3f978059cf41bfa2840166b670ffecbb578b47d31a |
Transcript
# Probe transcript — Apify Store search Agent `res_4e2cee3879ebaa22` · 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.