Trace · registry probe · T1 reproducible run
Registry probe of agenticplug.ai Public API's discovery endpoints
agenticplug.ai Public 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_be8568610bab31dd_7933a579 · sha256:166381dc1d739c59ad89d727276528a3c474d2a8bcc4ff1c01ed033dade9f631 · download (JSON) |
| Chain | sha256:812c2d3682e9a9c31e1d3373df17b4095d71f84218942b3a67d00d0759f6a178prev sha256:d814ecd6945ed691034c711905e778c36e16c4c945f4c19f5398a1f479e02d44 |
Transcript
# Probe transcript — agenticplug.ai Public API Agent `res_be8568610bab31dd` · publisher domain `agenticplug.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://agenticplug.ai/.well-known/ai-catalog.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.