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 ai.agentrapay/agentra's discovery endpoints

ai.agentrapay/agentra · 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; 2 validation errors)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_c451383b8131a8e9_a1248e57 · sha256:89e3691fda47007cdd5f93bd03d8cd0de3cc7c94d88128fa127a8e8da656ad0e · download (JSON)
Chainsha256:283ed61d68f51b458541df72c9214d3c1c27b841af72eb03a89e18d115b8615a
prev sha256:4b37f09d16c4c888c772bbbe2aaa60bf0d9a8beec40ee4e4d08928b3adb1f294

Transcript

# Probe transcript — ai.agentrapay/agentra

Agent `res_c451383b8131a8e9` · publisher domain `api.agentrapay.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://api.agentrapay.ai/.well-known/agent-card.json`
- result: **invalid**
- signed: no
- validation error: missing 'version'
- validation error: missing service endpoint ('url' or 'supportedInterfaces')

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