A

Protocol

HIGH

UCP profile declares a valid shopping service entry

UCP profile declares at least one shopping service with a recognised transport and an HTTPS endpoint. Without a valid shopping service entry, agents can recognise you as a UCP merchant but have no way to fetch your catalog.

What this check looks for

Walk the profile's `services` collection and locate every entry whose namespace identifies it as the shopping service (`shopping` or `dev.ucp.shopping`). At least one entry MUST declare a supported `transport` (rest, mcp, a2a, or embedded) and an absolute `https://` endpoint. Profiles without such an entry exist but are non-actionable for agents.

Which AI surfaces it affects

  • Google AI Mode (UCP)100
  • Microsoft Copilot70
  • ChatGPT (ACP)30
  • Meta AI30
  • Perplexity20

Weighted against the live specs — ACP 2026-04-17, UCP 2026-04-08.

How to fix it

Declare a shopping service entry with a recognised transport and an HTTPS endpoint

Shopify

Developer
  1. If your storefront exposes a UCP-compliant catalog endpoint via an app or proxy, declare it under `services[]` in `/.well-known/ucp` with `transport: "rest"` and the HTTPS endpoint URL.

Platform docs ↗

BigCommerce

Developer
  1. Add a `services[]` entry pointing at your BigCommerce-backed catalog API (or a UCP-adapter you host). Use `transport: "rest"` and an HTTPS endpoint.

Platform docs ↗

WooCommerce

Developer
  1. Expose your WooCommerce catalog via the REST API (or a UCP adapter plugin) and declare the endpoint in the shopping service entry.

Platform docs ↗

Custom / headless

Developer
  1. Add a shopping service entry to your UCP profile pointing at the HTTPS endpoint that exposes your catalog.
<!-- /.well-known/ucp (excerpt) -->
{
  "services": [
    {
      "namespace": "shopping",
      "version": "2026-04-08",
      "spec": "https://ucp.dev/2026-04-08/specification/shopping/",
      "transport": "rest",
      "endpoint": "https://example.com/ucp/shopping",
      "schema": "https://example.com/ucp/shopping/openapi.json"
    }
  ]
}

The spec it's pinned to

  • UCP overview — services declaration

    UCP profiles declare merchant capabilities under `services[]`. The shopping service (namespace `shopping`) advertises the catalog endpoint; without a recognised transport and HTTPS endpoint, agents cannot consume the catalog.

  • Google UCP profile — services structure

    Google's UCP guide requires the shopping service entry to declare a supported transport (rest, mcp, a2a, or embedded) and an absolute HTTPS endpoint so AI Mode can negotiate against it.

UCP shopping service specification ↗

Does your store pass this check?

Run the full audit — 82 checks across five AI shopping surfaces. Most tools only check whether you get mentioned; we check whether an agent can buy from you.

Related protocol checks

← All 82 checks