Registry probe of ARC (arcreport.ai): can an agent reach checkout?'s discovery endpoints

ARC (arcreport.ai): can an agent reach checkout? · 2026-10-19 · 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 verified (unsigned); ARD invalid (2 validation errors)

Transcript

# Probe transcript — ARC (arcreport.ai): can an agent reach checkout?

Agent `res_a2ffb923b0b3bbe3` · publisher domain `arcreport.ai` · 2026-10-19 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://www.arcreport.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 1.0 (card 1.1.0)
- signed: no
- skills advertised: precheck, find_agent_ready_stores, can_agent_checkout, ask_arc, agent_commerce_adoption, product_data_check, google_checkout_readiness, get_agent_facts, list_category_agent_facts, dataset_info, protocol_matrix, agent_leaderboard, submit_leaderboard_run, submit_store, store_card, validate_ucp_profile

## Agentic Resource Discovery (ARD)

- requested `https://www.arcreport.ai/.well-known/ai-catalog.json`
- result: **invalid**
- manifest entries: 2
- validation error: entries[0]: missing required term 'displayName'
- validation error: entries[1]: missing required term 'displayName'

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