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 BeevR public agent API's discovery endpoints

BeevR public 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

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_08506734bdd3f916_a5a10fbf · sha256:d7579252d977a8a35d8c6c05f9121e3df11a1fab59a32b6a6d8b81801aee767e · download (JSON)
Chainsha256:73adfb0b947d43de1ffedbe567fd660ef82d0e443f5dcac3e5e5851142f02584
prev sha256:00a6c8cfa6d41e0592b9600d7da4c433f81e3b7bba26b6750d85f8aadf7547bd

Transcript

# Probe transcript — BeevR public agent API

Agent `res_08506734bdd3f916` · publisher domain `beevr.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://beevr.ai/.well-known/ai-catalog.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.