Trace · registry probe · T1 reproducible run

Registry probe of Booqer's discovery endpoints

Booqer · 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); 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_c703bc4c6e44de89_644dfbfe` · `sha256:a79fb86f5b7ff16fb69cf516c223952e3af4274939b4429e47c06bc2e285a0b4` · download (JSON)
Chain	`sha256:ece9e7a116e45eee20d3fcf1b39467df77ce48adee555de1faf6d4ad99d29737` prev sha256:2a009a7f15ac2751e8bd1643cc115d785aea2a0f40b9eb20a632514ec26066cd

Transcript

# Probe transcript — Booqer

Agent `res_c703bc4c6e44de89` · publisher domain `booqer.ai` · 2026-10-25 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://booqer.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 1.0 (card 1.0.0)
- signed: no
- skills advertised: List verified shops, Open a shop booking page

## Agentic Resource Discovery (ARD)

- requested `https://booqer.ai/.well-known/ard.json`
- result: **verified**
- manifest entries: 1

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