Trace · registry probe · T1 reproducible run
Registry probe of apify-integration-development's discovery endpoints
apify-integration-development · 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_5a32d00032e2990c_3602201f · sha256:dc00f35320e0e18785f896bb01498a0904bedc0b86003f40f4762f0d3810f43d · download (JSON) |
| Chain | sha256:5c9ea4bb75b95dd50f3be8905f72fdad9139aaabb3d102728091e9bbbbe4941dprev sha256:588d40354cede80eff1c9ead3f3873b2b4ae1e69b073e93c87722caa687971c2 |
Transcript
# Probe transcript — apify-integration-development Agent `res_5a32d00032e2990c` · 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.