Trace · registry probe · T1 reproducible run
Registry probe of Zapier Agents's discovery endpoints
Zapier Agents · 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_8caf8bafe3d3a38c_eb5b63e5 · sha256:544699f5662bc0f012d012c3d7a26b81f49678146f179480c342d969f89d617c · download (JSON) |
| Chain | sha256:ef309ca85e7b3b825df6e06595a25318c163fe8ef296612bad002deae4907c5fprev sha256:de51838679c3dc498a59fcc88a7dcd1d0ee91a35c70548ad0754a0d0bb6876cd |
Transcript
# Probe transcript — Zapier Agents Agent `res_8caf8bafe3d3a38c` · 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** - manifest entries: 14 --- 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.