Trace · registry probe · T1 reproducible run

Registry probe of BeevR's discovery endpoints

BeevR · 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. A2A verified (unsigned); ARD verified

Entry	GET on the publisher's well-known discovery paths
Actions	served Agent2Agent (A2A) document; served Agentic Resource Discovery (ARD) document
Egress	no
Human approval	—
Secrets touched	no
Bundle	`bundles/tr_st_bb3c12727d17ec4f_3b46c792` · `sha256:0eda8951d4b51b54f8b7a53b85a7edd7c01c5583407fa4957eba56649efcebb2` · download (JSON)
Chain	`sha256:d814ecd6945ed691034c711905e778c36e16c4c945f4c19f5398a1f479e02d44` prev sha256:44ab24890b98afb2a1c0745ede3dee95ea848e0ccf4dd992d03ebd4f17f3e46b

Transcript

# Probe transcript — BeevR

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

## Agent2Agent (A2A)

- requested `https://beevr.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 1.0.0)
- signed: no
- skills advertised: Find BeevR expertise, BeevR pricing

## Agentic Resource Discovery (ARD)

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

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