Trace · registry probe · T1 reproducible run
Registry probe of Agentgates REST API (x402)'s discovery endpoints
Agentgates REST API (x402) · 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. ARD verified
| Entry | GET on the publisher's well-known discovery paths |
| Actions | served Agentic Resource Discovery (ARD) document |
| Egress | no |
| Human approval | — |
| Secrets touched | no |
| Bundle | bundles/tr_st_a5ff85736cd78a22_8e1cd277 · sha256:483121ec7fa5117f1c0cfe4603fccf3095016c39e71d583e18e1bc51c5f69df2 · download (JSON) |
| Chain | sha256:530e025cc4bc73f4cd01fadb0af3a8cca11ac7ff12b8c976301fda1bd7630949prev sha256:1fe83c8da70e7bca408dd3185d4a7a3f940cb91a5bb57536679c16995736cf26 |
Transcript
# Probe transcript — Agentgates REST API (x402) Agent `res_a5ff85736cd78a22` · publisher domain `agentgates.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://agentgates.ai/.well-known/ai-catalog.json` - result: **verified** --- 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.