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

Amdahl · 2026-10-19 · 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 apiKey, oauth2; unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_e5fbd7554b932967_a6307c68 · sha256:47ea08ed9ec473c56300e29379c0567afdd26fc3d5a6f9af1e8c383b420d279d · download (JSON)
Chainsha256:e91eb3f02d743a556cd32ed02ffd549b680113d79f4c0293dbd59060d7869250
prev sha256:c9fc5d65d9fa19d92f52102f47c3ddfac5608c985721023930f5ab4eede27d3e

Transcript

# Probe transcript — Amdahl

Agent `res_e5fbd7554b932967` · publisher domain `docs.amdahl.ai` · 2026-10-19 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://docs.amdahl.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.2.0 (card 1.0.0)
- auth schemes: apiKey, oauth2
- signed: no
- skills advertised: Optimize outbound messages, Grade GTM outputs, Search buyer data, Retrieve business context

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