Trace · registry probe · T1 reproducible run
Registry probe of Autoblogging.ai article writer's discovery endpoints
Autoblogging.ai article writer · 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_0357a336a4374fb8_08541083 · sha256:05443fac69c598e0780099cf3b73bc14f26da38179ec15b68defef4a2691235e · download (JSON) |
| Chain | sha256:605e84819522b7672c6a6d23e4759d70805c2c04f8fa6b09457c703731790e29prev sha256:6a0121f0b6d6b9047782febeaded831b5f4b1fc3acdbeae3ca218b9113e35567 |
Transcript
# Probe transcript — Autoblogging.ai article writer Agent `res_0357a336a4374fb8` · publisher domain `autoblogging.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://autoblogging.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.