Trace · registry probe · T1 reproducible run
Registry probe of Pydantic Documentation Search API's discovery endpoints
Pydantic Documentation Search 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_83543c823fb3896e_c7b97605 · sha256:f82693cb3e2c1fd8953bfa108ae7e5713e716f07a71ab33a23245ef881fa5afa · download (JSON) |
| Chain | sha256:d27ed7c4c18c5d138075f3e0b68d78102e78e3648916d7d2055e3227d3b6c787prev sha256:c35dd83ffb8a57faa0d62a2ec6cf9f78d0d1efdadaf3ef51ae1f7c43a37bc609 |
Transcript
# Probe transcript — Pydantic Documentation Search API Agent `res_83543c823fb3896e` · publisher domain `pydantic.dev` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://pydantic.dev/.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.