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

Aginera · 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 oauth2; unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_df838db66caa8938_5718116f · sha256:e06267c0c1169f628966b9733cd81298a2fb2a3f897ae55b55f9d63d3cf6c9f1 · download (JSON)
Chainsha256:04fe85ba0b474af68186cb17d38bca2db7564563290688ba66ae39351130bfd5
prev sha256:37e81c2e4898754f9d8dbeba9d4d70ab75be10015a214ea99548d4b24d10a44c

Transcript

# Probe transcript — Aginera

Agent `res_df838db66caa8938` · publisher domain `aginera.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://mcp.aginera.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 1.1.0)
- auth schemes: oauth2
- signed: no
- skills advertised: Quantity takeoff, Measured routes, Schedules, PDF to CAD conversion, Export

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