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

Auxen · 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 (auth auxenKey; unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_b4c24a2e3da15623_f1dbc1ea · sha256:fd173c671a6a20402b18ff5fd21b00cb5bbbae114a797c7513f08ccf57603028 · download (JSON)
Chainsha256:f53dc536e0591f1bc2361bc8c67282b2359da925ba068506c5e00a1f008f94bc
prev sha256:11a83011fbbc3414c2038ef6706bc18932924adbbc10310ad47b0c54bbbd2b10

Transcript

# Probe transcript — Auxen

Agent `res_b4c24a2e3da15623` · publisher domain `auxen.ai` · 2026-10-25 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://auxen.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 1.0 (card 1.0.0)
- auth schemes: auxenKey
- signed: no
- skills advertised: Hire a worker, Message a worker, Check or stop a worker

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