Trace · registry probe · T1 reproducible run
Registry probe of Pydantic API Catalog's discovery endpoints
Pydantic API Catalog · 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_532fed6cb505a327_4d5abccf · sha256:cb4442ed09e0eb51dad5134e7407cac3e750b1665b88d9e09f961b143b2b6664 · download (JSON) |
| Chain | sha256:9c5ff6d4d653d0a560f19e7ee0171e888da47e832d1e4166c9572a01d3a4ae9cprev sha256:413e56f70b3527cfe996059729e6c147bbc6b03d9c38ef9ea53b7ac5a15f5804 |
Transcript
# Probe transcript — Pydantic API Catalog Agent `res_532fed6cb505a327` · 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.