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 Advisors AI — Route a Store Need to a Service's discovery endpoints

Advisors AI — Route a Store Need to a Service · 2026-10-12 · 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)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_74c09a764102c302_e268d904 · sha256:453f314c20cc5058c6c81da6e356de0e8c9de3cdac6f231e7f6e1f61565117ef · download (JSON)
Chainsha256:145a5cf6c01643d6496bb64663f7b3e0a53afe35a2e6ce346ca8048415074cad
prev sha256:b516e54ffd3e461641cc3d8988551e7197a7ca25c3f3690ec4b66fe00e227696

Transcript

# Probe transcript — Advisors AI — Route a Store Need to a Service

Agent `res_74c09a764102c302` · publisher domain `advisorsai.ai` · 2026-10-12 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://advisorsai.ai/.well-known/agent-card.json`
- result: **invalid**
- signed: no
- skills advertised: Store readiness check, Service navigator
- validation error: missing 'version'

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