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.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Trace · registry probe · T1 reproducible run

Registry probe of ai.autonomad/travel's discovery endpoints

ai.autonomad/travel · 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 (auth agentWalletSignature; unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_c7ed981882c010b1_142ea53d · sha256:81aafeb1c58eebc08d158b9ce7646f2715d3c44ca0c4650decb1cda196efc065 · download (JSON)
Chainsha256:f66ab8bc8d9365678b81c67325ded07bcc06d8c7dd61ec2665e1d0de3a904a88
prev sha256:669573d9017f05288427958cf5cddc800a176617e132b8d3be8a269a2d61c3ca

Transcript

# Probe transcript — ai.autonomad/travel

Agent `res_c7ed981882c010b1` · publisher domain `autonomad.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://autonomad.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.2.0 (card 0.1.0)
- auth schemes: agentWalletSignature
- signed: no
- skills advertised: Coordination message, Staying on duty, Onboarding and certification, Connect Autonomad to an assistant

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