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

apify-ultimate-scraper · 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_400cf0d43f56c089_06a3b119 · sha256:eb34dd341db581ee3bb18333936b64a48102d00ef571876dbd4d024819ff33e4 · download (JSON)
Chainsha256:42f6a77372e461f7dbbc7654262b1b3e5d43a70fc20b78479b911574137607ca
prev sha256:a70977440082bf0b01ba137a568721a42cbabefc534d58c5b979caa9b1a1d949

Transcript

# Probe transcript — apify-ultimate-scraper

Agent `res_400cf0d43f56c089` · 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.