Trace · registry probe · T1 reproducible run
Registry probe of Infisical REST API's discovery endpoints
Infisical REST API · 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_af864917c301d3c5_17793e5b · sha256:b762a2d95256a6d2115cf6a4e0399c0b6316742befe6b1753bacfdffb8ca60ff · download (JSON) |
| Chain | sha256:89041515da550d3caa2a276308c1e3924b3e860cbdc023dd17b55d3a1fb2739aprev sha256:c1455ddd32d974458c84fda7181a3ef6b3bbd00b5bfb5e6534f31e7471b683d6 |
Transcript
# Probe transcript — Infisical REST API Agent `res_af864917c301d3c5` · 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.