Publishing a UCP profile

Here is exactly what the work is, what we take on, and where the honest limits are. Read the last section before you decide.

Why this is not just a file upload

No redirects allowed. The spec requires the profile to be served at /.well-known/ucp on your own domain, directly. Pointing that path at someone else's server with a 301 fails discovery, which rules out the workaround most hosted platforms leave you.
Version matching is exact. UCP versions are dates. The spec moved from 2026-01-11 to 2026-04-08 to 2026-08-25 in eight months. A profile pinned to an old version simply stops negotiating, with no error anywhere you would see it.
A profile is a promise. Every service you declare has to answer. Declaring a checkout you have not built is worse than declaring nothing, because agents will try it and fail.

The shape of what gets published

A profile for your store would look like this. Note supported_versions, which keeps older agents negotiating while you move forward.

{
  "ucp": {
    "version": "2026-08-25",
    "services": {
      "dev.ucp.shopping": [
        {
          "version": "2026-08-25",
          "spec": "https://ucp.dev/2026-08-25/specification/overview/",
          "transport": "rest",
          "endpoint": "https://edge.storedeploy.com/u/<your-id>/shopping",
          "schema": "https://ucp.dev/2026-08-25/services/shopping/openapi.json"
        }
      ]
    },
    "capabilities": {
      "dev.ucp.shopping.order": [
        {
          "version": "2026-08-25",
          "spec": "https://ucp.dev/2026-08-25/capabilities/order/",
          "schema": "https://ucp.dev/2026-08-25/capabilities/order/schema.json"
        }
      ]
    },
    "payment_handlers": {},
    "supported_versions": {
      "2026-04-08": "https://yourstore.com/.well-known/ucp/2026-04-08"
    }
  },
  "keys": []
}

Where we are today, plainly

The scanner is finished and free, and it is accurate: it validates against the published spec and refuses to grade a store it could not read.

The managed profile is being built now, and we are taking a first group of stores. We are not charging for it until the shopping service behind it answers correctly, because a profile that declares a service it cannot honour would make your store look broken to an agent rather than invisible. Invisible is better than broken.

Leave your domain and we will come back to you when it is live, with pricing and a migration path. No charge, and nothing to cancel.

Join the first group

Email us your domain and the platform it runs on. A person reads it, and you get a straight answer about whether this is worth your money, including when it is not.

Email hello@storedeploy.com

We hold your address only to reply. No list, no sequence, no sharing.

Meanwhile, things worth fixing today

Three of the four checks are entirely in your hands and cost nothing: unblock the AI shopping crawlers in robots.txt, put a complete schema.org Product block with price, currency and availability on every product page, and publish a sitemap your platform keeps current. The scan lists each one against your store, with the fix.

Run the scan