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 Infisical vs. HashiCorp Vault's discovery endpoints

Infisical vs. HashiCorp Vault · 2026-10-25 · 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_9808b7d1a45ab227_7c2493e1 · sha256:ddcc2f475b75db7cc2d169a1ebabe62e6eacf7914b88399abcd6a9362eed95ee · download (JSON)
Chainsha256:0911bf70846c1ffea27b8fe4c3e19dee7b15e8a8985d7385f762ca128976519d
prev sha256:7f84b39217d66f5fa62052642ec2a0d822d3f5007ece59100695a45a2b3cefed

Transcript

# Probe transcript — Infisical vs. HashiCorp Vault

Agent `res_9808b7d1a45ab227` · publisher domain `infisical.com` · 2026-10-25 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://infisical.com/.well-known/ard.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.