Trace · registry probe · T1 reproducible run
Registry probe of Apify site index (llms.txt)'s discovery endpoints
Apify site index (llms.txt) · 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_b2635b96a46f53fd_5b7d0c78 · sha256:55110c6ec185d87c00ae739e28c2d690ebda70171ab656083b93125c5b74d314 · download (JSON) |
| Chain | sha256:c236ef266a806f4117aa4628c39dfb4c53779ce6ee63a45a06e3bbf010b8e23aprev sha256:6ffd7108ec8a2a4c5c31ba184f350b6689b250cbd4d29517da774ce8bba1555b |
Transcript
# Probe transcript — Apify site index (llms.txt) Agent `res_b2635b96a46f53fd` · 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.