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 agent-bev · audit's discovery endpoints

agent-bev · audit · 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_c85905822ab1c98c_cfb4f739 · sha256:efa96299bbf7330d83dec435956d7de066a36b3fda74781e304d51cca8af4e60 · download (JSON)
Chainsha256:d48fdabaee77792646ae5a7a730272bab7a63269a6d9a74dcfae3f3c97a6a7b2
prev sha256:3107279f040af8fb2be0841913fa82fa07914b78107acad9c0e4bc6ba3723b38

Transcript

# Probe transcript — agent-bev · audit

Agent `res_c85905822ab1c98c` · publisher domain `agent-bev.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://agent-bev.ai/.well-known/ai-catalog.json`
- result: **verified**
- warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search)

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