Trace · registry probe · T1 reproducible run
Registry probe of Zapier Platform CLI's discovery endpoints
Zapier Platform CLI · 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_43e9afe968126e00_3e39a335 · sha256:f16a340bd1326eeccf01e405a0a54bf860b7e3ec01c4209373cb73758b1cddff · download (JSON) |
| Chain | sha256:664539999a7e5f4e2e68d295a0de26d91917ca807656b17efe44d0f74cee2874prev sha256:42f6a77372e461f7dbbc7654262b1b3e5d43a70fc20b78479b911574137607ca |
Transcript
# Probe transcript — Zapier Platform CLI Agent `res_43e9afe968126e00` · publisher domain `zapier.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://zapier.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.