Trace · registry probe · T1 reproducible run
Registry probe of apify-actor-development's discovery endpoints
apify-actor-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_9df573d40b49da64_3cf0c0e8 · sha256:81525dc7036a1ecdbbfaa609ef67c602bcb49b44db2053d0c3ab5203842ee545 · download (JSON) |
| Chain | sha256:9387c8e0f50382ec9e9f1ea4198211886ac69df54dc478975f3d5c362d65906aprev sha256:47652e8e19f60b0a115fddd8b2ce2a3b07e2d3f4915e7d9284d8bdb53780d310 |
Transcript
# Probe transcript — apify-actor-development Agent `res_9df573d40b49da64` · 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.