Trace · registry probe · T1 reproducible run
Registry probe of Zapier Partner API's discovery endpoints
Zapier Partner API · 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_220d5778707bb544_1220af7f · sha256:31b199dcc1549a79e50cb0c753ef3858ff74935a19eb8c9e401b4c291f25ce47 · download (JSON) |
| Chain | sha256:8aa6d546c99ed1fb2dad01ddbf40835303f0b341d2f2fbe59c997eb6856a3691prev sha256:4cdbcaf526f6e8d615a7fb227e286c842369f0b099ece6652d6c0f2c82da5ec5 |
Transcript
# Probe transcript — Zapier Partner API Agent `res_220d5778707bb544` · 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.