Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
Trace · registry probe · T1 reproducible run

Registry probe of Zapier Connectors's discovery endpoints

Zapier Connectors · 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

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_2be8feabffe986b7_df0e210d · sha256:b701cfc68f5d888dde9a16696f8889ba7aba26fd1af73882569d6f355575ee98 · download (JSON)
Chainsha256:00241b15006516257567ed983c2c2f297174738990c3a784487feeca471a2c31
prev sha256:9dfbca363aa278312f13fb1fce86b9ba893c817633a35aca0e4d58c070ff13f3

Transcript

# Probe transcript — Zapier Connectors

Agent `res_2be8feabffe986b7` · 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.