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 Ankra's discovery endpoints

Ankra · 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)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_c8f97e3daa5d7a16_19cbdc88 · sha256:768a78d23ec88ec1d4ccb2117917ef7bdc71062541c99671ea679580c9b439cd · download (JSON)
Chainsha256:0507a3be8e6ef22c6fc4001a16de65cd53a7275c0404bb3986ff77dcf8643f77
prev sha256:d48fdabaee77792646ae5a7a730272bab7a63269a6d9a74dcfae3f3c97a6a7b2

Transcript

# Probe transcript — Ankra

Agent `res_c8f97e3daa5d7a16` · publisher domain `docs.ankra.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://docs.ankra.ai/.well-known/agent-card.json`
- result: **invalid**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: ankra
- validation error: missing 'description'

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