Trace · registry probe · T1 reproducible run
Registry probe of Zapier Public API Reference's discovery endpoints
Zapier Public API Reference · 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_471283927f386437_5c2da045 · sha256:bc64805a895d4cff8ab8c87210fd81293cefe6d54ba4c03662da687a331a889a · download (JSON) |
| Chain | sha256:4dbc68a542f922ac95a15f04acbe8bc131e02f200c1cbaab5a06543653a8b773prev sha256:d24e815cf23999a8dc2a6ced94f1e2509fd0f0a74b20dca55d8d20502a9845c8 |
Transcript
# Probe transcript — Zapier Public API Reference Agent `res_471283927f386437` · 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.