Trace · registry probe · T1 reproducible run
Registry probe of AutoPoster AI Agent API's discovery endpoints
AutoPoster AI Agent 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_83e66a7b82df70cb_e13e8435 · sha256:970965f63d297c4f8c843b67da42af87ce9499884e2dd749452cb496a94be119 · download (JSON) |
| Chain | sha256:23a87e5db6224a657e85740313e4519c3ab98bfe8e0477df0505a9472bd48fa7prev sha256:cc2caf80dfe4e0ba4be0256ac5f41e0fc841acd0b092af0b679786ac02ff033c |
Transcript
# Probe transcript — AutoPoster AI Agent API Agent `res_83e66a7b82df70cb` · publisher domain `autoposter.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://autoposter.ai/.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.