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.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Trace · registry probe · T1 reproducible run

Registry probe of Autoposting's discovery endpoints

Autoposting · 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. A2A invalid (unsigned; 1 validation error)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_72f948bddb0b523a_32fa7410 · sha256:2a01e9d1963da4e262c54ebf4b94293146149df97eea026e6ec514ea76246c7e · download (JSON)
Chainsha256:fe6f5058255cc7ffb76125bdeea0387b013dde66a599cb89b13640d8a6aa8020
prev sha256:b9b270e70694393f76b2974d87a323f650e66d3289389faedae48a1e324b1dab

Transcript

# Probe transcript — Autoposting

Agent `res_72f948bddb0b523a` · publisher domain `docs.autoposting.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://docs.autoposting.ai/.well-known/agent-card.json`
- result: **invalid**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: autoposting
- validation error: missing 'description'

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