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 AutoRFP.ai developer documentation's discovery endpoints

AutoRFP.ai developer documentation · 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

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_01df3f54736dc5ce_087c5ee8 · sha256:ee94cc03f6074f9fc2f96c9f7e0a37b592ecf67ec6b764096585bae4cce1faf8 · download (JSON)
Chainsha256:e0b293b6b538eef06f9f7cfa8e5d4ab59eb675a9ae1484b5451fa8ee394dff68
prev sha256:0c0c538f4cc0790e47c5d0663f1a15c7a1533800e845e449c7455a6425d9d9e3

Transcript

# Probe transcript — AutoRFP.ai developer documentation

Agent `res_01df3f54736dc5ce` · publisher domain `autorfp.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://autorfp.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.