A2A agent card discovery: AI Catalog is now preferred
A2A v1.1.0-rc docs now prefer /.well-known/ai-catalog.json over agent-card.json, which can advertise only one Agent Card per domain.
Research topic
Discovery
9 sourced articles on discovery, newest first: what changed, what it means for an online store, and what to fix so an AI agent can still find, understand and buy there.
ARD trust manifest attestations: a scan is not a compliance badge
ARD's spec now says a SOC 2 attestation covers the publisher, while a security scan must name the artifact by digest. Here is what stores should claim.
ai-catalog.json is now ard.json: ARD v0.91 path change
ARD v0.91 moves the discovery manifest from /.well-known/ai-catalog.json to /.well-known/ard.json; consumers need not read the old path any more.
Does llms.txt Help AI Agents? Data From 1,033 Real Runs
A dataset of 1,033 traced AI agent runs shows llms.txt doesn't change whether a page can be fetched, but it does change what agents do next.
"llms.txt for E-Commerce: What to Put In It, With an Example"
The llms.txt spec shipped a v2 revision on August 10, 2026 adding link relations for discovery; here is what an online store's file should contain.
The A2A Agent Card: What agent-card.json Must Contain
The Agent2Agent protocol requires servers to publish a JSON Agent Card at /.well-known/agent-card.json describing their identity, skills and endpoints.
AI agents and e-commerce: what a competition regulator found
France's competition authority projects AI agents will carry 20-25% of e-commerce traffic by 2030 and names missing standardised data as the barrier.
Cloudflare's Agent Readiness Score: what it actually checks
Cloudflare's free Agent Readiness Score checks for a commerce discovery file, but never attempts an actual agent-driven purchase.
ai-catalog.json: make your store discoverable to AI agents
Google, Microsoft and nine others shipped Agentic Resource Discovery: one public ai-catalog.json tells agents what you sell. Almost no store has one yet.
📡 The agentic-commerce brief
What changed in the protocols — and what it means for your store. Connect it to your agent and it pulls the latest itself; no inbox required.
Add it to your agent (Claude Code, Claude Desktop, Cursor — anything that speaks MCP):
MCP server config
{
"mcpServers": {
"agentready-brief": {
"type": "http",
"url": "https://www.agentready.market/mcp/docs"
}
}
}Then ask it for the AgentReady brief —
it calls get_agentready_brief and reads any entry in full. Prefer a feed
reader? Subscribe by RSS.
No agent? Get it by email instead
Email delivery isn't live yet — nothing will land in your inbox until it is. Leave your address and you'll be on the first issue when it ships.