Trace · registry probe · T1 reproducible run
Registry probe of Paradev API's discovery endpoints
Paradev API · 2026-10-26 · 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_445de58a6f908b3d_e6050a47 · sha256:f87d66a12e14ffcd85b58c2b8c988ddcd7edf5c530492b9a7b9126a6efe8dc86 · download (JSON) |
| Chain | sha256:997e9047893deb9e979eba5dd05ab4a5d0724110f6cfeb465e6312393816ac83prev sha256:0ae8aa5910f027f7bba76d3f0ca7131a84785d7b2012c0bb0769d5d6508ce6a6 |
Transcript
# Probe transcript — Paradev API Agent `res_445de58a6f908b3d` · publisher domain `paradev.com` · 2026-10-26 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://paradev.com/.well-known/ai-catalog.json` - result: **verified** - warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search) --- 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.