Trace · registry probe · T1 reproducible run
Registry probe of Infisical vs. Keyfactor's discovery endpoints
Infisical vs. Keyfactor · 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
| 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_fd14ea858e4cdf08_d051892c · sha256:5c1bc10407a7a2d4ec79f90ffd4e817dfe94687e6da64c82cd5f06ebb2e3818f · download (JSON) |
| Chain | sha256:d53c9d07a7e5f000b9273c035aaf82c8824d38f1af5808e565c293596e4dbf6bprev sha256:2bd310188e756f2e398c32e18e8f14db7640763d9bb65ca0c786a1e80a9bb0a1 |
Transcript
# Probe transcript — Infisical vs. Keyfactor Agent `res_fd14ea858e4cdf08` · 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.