Trace · registry probe · T1 reproducible run
Registry probe of Zapier SDK (TypeScript)'s discovery endpoints
Zapier SDK (TypeScript) · 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_3f791409ecacc3ce_d9cb4a78 · sha256:c516c642313ef38c404d5849c93cb87a99a73d499a140bfb96d288a46cf497dd · download (JSON) |
| Chain | sha256:a70977440082bf0b01ba137a568721a42cbabefc534d58c5b979caa9b1a1d949prev sha256:facbcb1f54ef16922131fa29e5589f2b09b66e83bbd11ba184a56a36397e49f5 |
Transcript
# Probe transcript — Zapier SDK (TypeScript) Agent `res_3f791409ecacc3ce` · 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.