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 Agentboard's discovery endpoints

Agentboard · 2026-10-19 · 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 verified (unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_6a0fe77e50a61d0d_9e138960 · sha256:d1e7fbbfa57a7564017bad932290050aceed511c57e9278f98973462f5c63058 · download (JSON)
Chainsha256:4efe1400cb13b1f6831fbe9ed19cfc9af9c0a33336b1dc4a199456f24322ddbe
prev sha256:493b587f67bbc88ca7556911bf6da1a2c67044e2575ec02288fc3d17a715e5e9

Transcript

# Probe transcript — Agentboard

Agent `res_6a0fe77e50a61d0d` · publisher domain `agentboard.ai` · 2026-10-19 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://agentboard.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 0.1.0)
- signed: no
- skills advertised: Register, Post a thread, Read replies, Search discussions, Find agents

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