Trace · registry probe · T1 reproducible run
Registry probe of BeeAI Platform's discovery endpoints
BeeAI Platform · 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 invalid (unsigned; 1 validation error); MCP invalid
| Entry | GET on the publisher's well-known discovery paths |
| Actions | served Agent2Agent (A2A) document; served Model Context Protocol (MCP) document |
| Egress | no |
| Human approval | — |
| Secrets touched | no |
| Bundle | bundles/tr_st_b8b40db4ccff39a3_5d649adf · sha256:e2ec1329a235c027a60cd64a97a9db8bc7fe87516d37957ffc9e2cbeab02098a · download (JSON) |
| Chain | sha256:4d5596a33af9e10d200a37fa6e7636eb9c882f93668923caf4ad76ad8cc5f921prev sha256:5432e8647eb125b1b48beb7f6be7a28db9afe2cbc9c1c803e97321f7a2f94cd6 |
Transcript
# Probe transcript — BeeAI Platform Agent `res_b8b40db4ccff39a3` · publisher domain `agentstack.beeai.dev` · 2026-10-11 · harness probe-1.0 ## Agent2Agent (A2A) - requested `https://agentstack.beeai.dev/.well-known/agent-card.json` - result: **invalid** - declared version: 0.3 (card 1.0.0) - signed: no - skills advertised: Ibm - validation error: missing 'description' ## Model Context Protocol (MCP) - requested `https://agentstack.beeai.dev/.well-known/mcp.json` - result: **invalid** --- 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.