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 Pricing's discovery endpoints

Pricing · 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_71d26e9785642535_83856a6a · sha256:1ea0c07ef2dd73c12b41634f6017591940010cb30375064745cae8f73ffb0f9f · download (JSON)
Chainsha256:04b29106fedea8e59e87ae4592b7778881f2c478e080520678d210eb9839d455
prev sha256:214e3a8a86ac7be52504f618456176a3097c8f2dc86709d266e19174aae4a957

Transcript

# Probe transcript — Pricing

Agent `res_71d26e9785642535` · publisher domain `infisical.com` · 2026-10-11 · 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.