Trace · registry probe · T1 reproducible run
Registry probe of Apify API v2's discovery endpoints
Apify API v2 · 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_78d690fd4e3ba2e0_f1d9e807 · sha256:e867380a00ca9f9b6a5bed5ff9539bca220518d75958b7e5ee7f488860352ee4 · download (JSON) |
| Chain | sha256:2e7472c4c7dcf852f160a6be13c193d9c7b95af5bc42687906321b68540ca072prev sha256:6399807701908fb26e480d8a01ac1f38b759eecf7686a6794a849d6b0cc4208d |
Transcript
# Probe transcript — Apify API v2 Agent `res_78d690fd4e3ba2e0` · 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.