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

AgentMesh · 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_b25b7f91663f53e7_1748d7cd · sha256:a3eefa6675cdb5f7ffe076e210e8a9bffe53213d18e92b0cdac781ed43b248aa · download (JSON)
Chainsha256:6ffd7108ec8a2a4c5c31ba184f350b6689b250cbd4d29517da774ce8bba1555b
prev sha256:1859d273224fd8c3cc9fae3e49d3372ddf14f436a7a44673e1aebcc4c8a58717

Transcript

# Probe transcript — AgentMesh

Agent `res_b25b7f91663f53e7` · publisher domain `agentmesh.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://agentmesh.ai/.well-known/ai-catalog.json`
- result: **verified**
- manifest entries: 2

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