Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
Trace · registry probe · T1 reproducible run

Registry probe of Autoblogging.ai's discovery endpoints

Autoblogging.ai · 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

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_0c3793ef9503f37e_8855df3e · sha256:9da0c8ca46fb442e7ff59ef58317395eb158dfdccc8a22ff794a9cd218171cf8 · download (JSON)
Chainsha256:7ad7b52099995e71bb5473211348053ba4e363b59292d95f68aee0253ac7108a
prev sha256:b377b081753281a7f06bb5cc5e69a48b337089ab5f039ede7a4891d762b9831d

Transcript

# Probe transcript — Autoblogging.ai

Agent `res_0c3793ef9503f37e` · 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**
- manifest entries: 1

---
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.