Trace · registry probe · T1 reproducible run
Registry probe of Apify API catalog's discovery endpoints
Apify API catalog · 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_17b7c0aff78bfcd1_59a0fb43 · sha256:504e8cc875910a40c0a4e585e38d1f3048c5c7541903b94d70c9a6e2863efa7d · download (JSON) |
| Chain | sha256:ded8ee3c666db08699f3c205e6f6fdc245d0dba37c246b82b87e3ec9d8515a6dprev sha256:0fd4de62124d7ee4fccfd61ca4b80b2d27fe61b25b8afb6570e4527c3f164753 |
Transcript
# Probe transcript — Apify API catalog Agent `res_17b7c0aff78bfcd1` · 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** - 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.