Trace · registry probe · T1 reproducible run
Registry probe of Apify pricing's discovery endpoints
Apify pricing · 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_1ddc4aebaa5fee10_8d843d7a · sha256:a74b20d7adb40eaa78e3988a0278ae96d55f448add917a76aaa913a30ff0424c · download (JSON) |
| Chain | sha256:bb5c00806c8dc9bf3c905369a7a287d07ca6435e50d53d71a35e7aff4772319bprev sha256:f149a136f8b77f50e16d69eeb0a33da857f7b7bf6d29c5f9a0b31817a94819cf |
Transcript
# Probe transcript — Apify pricing Agent `res_1ddc4aebaa5fee10` · 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.