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 Install Zapier (router)'s discovery endpoints

Install Zapier (router) · 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_b6f04cddff0d0274_d546c19d · sha256:82abebd57eefcc26e3d75eb698b1f0ec4ba89d589882bcb36c65b1b1d577db2d · download (JSON)
Chainsha256:936997a8ca4b141211be886f4b239ada9d5d8ec78bcda08f3b34393cd5254bab
prev sha256:622aa72707688348fa1b22bc1939223bf21f9def97e28094811f37663793f644

Transcript

# Probe transcript — Install Zapier (router)

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