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

APIANT · 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. ARD verified

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_735b2cb88ce8d05c_cff8114a · sha256:bccc2e062bdd98f19f0bf6f81eff69094ad1a0b67dc3f33771acd2901de67c14 · download (JSON)
Chainsha256:4bed06f126bc3a791c258116a75c659f1d51c9724ee94dab514119ab39d0c916
prev sha256:bfef2c70cab1c7e2dac362de3cbc59e8a2b81b8b4062681cc367c14a50328742

Transcript

# Probe transcript — APIANT

Agent `res_735b2cb88ce8d05c` · publisher domain `apiant.ai` · 2026-10-25 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://apiant.ai/.well-known/ard.json`
- requested `https://apiant.ai/.well-known/ard.json`
- result: **verified**
- manifest entries: 6

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