Browse topics

Readiness and feeds

Readiness scoring measures how well your commerce and agent-facing surfaces are set up for AI shopping and discovery—grounded in feed snapshots and optional store signals.

What readiness measures

Readiness looks at structured data in your feeds (for example product feeds and ACP-style sources), policy and checkout-related signals where configured, and how they line up with what AI agents need to quote prices, availability, and trust signals accurately.

Scores and issues are organization-scoped in the product but surfaced in the notebook experience tied to your org.

Feed snapshot

Before running a readiness audit, complete feed setup in the dashboard: upload or connect a feed so the system can snapshot your catalog or relevant SKU data. Without a snapshot, readiness run endpoints return an error explaining that setup is incomplete—the same applies when calling readiness via MCP.

MCP

Use tools like readiness.run_audit, readiness.get_scores, and readiness.list_issues once a feed snapshot exists for the org linked to your notebook.

Running a readiness audit

From the dashboard, open Readiness for your notebook and start an audit after feeds are configured. Review the score breakdown and work through prioritized issues.

UCP and checkout

Where UCP (Universal Commerce Profile) or checkout tests are part of your plan, connect the domains and flows described in-product so readiness can evaluate agent-actionable endpoints and purchase-related clarity. Follow the latest labels in the Readiness area of the dashboard.

More on agents and automation: MCP and AI agents.

Search documentation

Jump to a docs page