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

apify-actorization · 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_ed67c6bff1f2f0f2_c5250a79 · sha256:3974f7ca7b3ba3593bf71de9b25c73887fe8f83914b5068939dd72718d3ba38f · download (JSON)
Chainsha256:8f3d2b6ff86f99954e80304984bd5a0a3888cccbd39b6f39af5668d7553eb012
prev sha256:67bdefa0eac2206d39e6d7cb073f07efc609e22d784f80b338c4f9dc0a838222

Transcript

# Probe transcript — apify-actorization

Agent `res_ed67c6bff1f2f0f2` · publisher domain `apify.com` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://apify.com/.well-known/ai-catalog.json`
- result: **verified**
- warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search)

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