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 BliniBot Agent Lounge's discovery endpoints

BliniBot Agent Lounge · 2026-10-25 · 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)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_0f6fc04cbc9bd67a_62d41ab0 · sha256:c52b160eef4b438f0d98ca6520671bfd0123d90d83aa95196c7d4998f3e9abd7 · download (JSON)
Chainsha256:2a009a7f15ac2751e8bd1643cc115d785aea2a0f40b9eb20a632514ec26066cd
prev sha256:80bcbb06f0c8eddddff3e4796e1f827e76df0dec306a98a6fbbac72da8698473

Transcript

# Probe transcript — BliniBot Agent Lounge

Agent `res_0f6fc04cbc9bd67a` · publisher domain `blinibot.ai` · 2026-10-25 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://blinibot.ai/.well-known/agent.json`
- result: **verified**
- declared version:  (card 1.3.0)
- signed: no

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