Every Wix store we check publishes a UCP profile, the file at /.well-known/ucp that tells AI shopping agents what a store sells and how to buy from it. The merchant doesn't install anything. Wix serves the profile from its own platform, and in our census Wix is the second-largest source of valid UCP profiles after Shopify.
This guide covers what that profile contains, what an agent can actually do with a Wix store today, and how to check your own store, step by step, in UCP Checker and UCP Playground.
Does Wix support UCP?
Yes. Wix publishes a UCP profile for the Wix sites we check, generated by the platform rather than set up by the store. As of our October report, about 6,700 Wix stores in our census published a valid one, and Shopify and Wix together carried about 92% of verified stores.
Wix's own agentic commerce pages focus on other routes. Wix describes itself as an official signatory of the Agentic Commerce Protocol (ACP), and points eligible merchants to Stripe's Agentic Commerce Suite and to PayPal's agentic commerce services. UCP appears there as one of several relevant protocols. So if you've read that Wix "isn't on UCP", that reflects Wix's own pages rather than its stores: the profile is live either way.
What Wix sets up for you
A Wix profile follows the same template on every store. Trimmed to its shape:
{
"ucp": {
"version": "2026-04-08",
"services": {
"dev.ucp.shopping": [
{ "transport": "rest", "endpoint": "https://www.wixapis.com/ecom/ucp/<site-id>" },
{ "transport": "mcp", "endpoint": "https://www.wixapis.com/ecom/ucp/<site-id>/mcp" }
]
},
"capabilities": {
"dev.ucp.shopping.catalog.search": [ … ],
"dev.ucp.shopping.catalog.lookup": [ … ],
"dev.ucp.shopping.cart": [ … ],
"dev.ucp.shopping.checkout": [ … ],
"dev.ucp.shopping.fulfillment": [ … ],
"dev.ucp.shopping.discount": [ … ]
},
"payment_handlers": {}
}
}
Three things to notice:
- The endpoints live on
wixapis.com, not on your domain. Your domain serves the profile; Wix's API answers the calls, one site ID per store. - Two transports: REST and MCP. Agents built on the Model Context Protocol can talk to a Wix store directly.
payment_handlersis empty. That means agents don't pay inside the conversation; payment happens on your own checkout page (more on that below).
What Wix stores declare
Because it's one template, every valid Wix profile declares the same thing. From our Wix platform page:
| Wix stores declaring it | |
|---|---|
| Catalog search and lookup | 100% |
| Cart | 100% |
| Checkout | 100% |
| Fulfillment and discount | 100% |
| Order, identity linking | not declared |
| REST and MCP transports | 100% |
The average UCP Score for Wix stores is in grade A. Within the platform, stores score within a point or two of each other, since they all declare the same template.
What an agent can do with a Wix store today
We connected to the MCP endpoint of a sample of 16 Wix stores from our census and walked each one as an agent would. Every store ran the same Wix server and listed the same eight tools:
search_catalog,lookup_catalog,get_productcreate_checkout,get_checkout,update_checkout,complete_checkout,cancel_checkout
What happened next:
- Search and product details work. Real stores returned their products with prices, variants, stock status and images.
- An agent builds a checkout directly. There are no cart tools on the MCP server, even though the profile declares cart, so an agent goes from product to
create_checkout. On 9 of the 11 stores that had products, that returned a priced checkout with line items, totals and shipping. - Payment hands off to your site. Those checkouts came back as
requires_escalationwith the messagepayment_requires_site_checkoutand acontinue_url: the agent sends the buyer to your Wix checkout page to pay. This is a normal UCP pattern, and it's the one most stores use today. - Two stores had no checkout page set up, which Wix reported as
CHECKOUT_PAGE_NOT_FOUND, so there was nothing to hand the buyer to. - Not every Wix site is a shop. Four returned no products at all, and one still carried Wix's sample catalogue ("I'm a product"), whose items can't be bought. Wix publishes the profile either way, so a valid profile on its own doesn't mean there's anything to sell.
Two more ways in: Wix's site MCP and NLWeb
UCP isn't the only door Wix opens for agents. On the Wix stores we checked, two more sit beside it:
| Where | What it does | |
|---|---|---|
| UCP | /.well-known/ucp, calls go to wixapis.com |
Commerce: catalog, checkout, the handoff to your checkout page |
| Wix site MCP | /_api/mcp, listed in your site's llms.txt |
A general site assistant server with tools to search the site, get business details and call the site's Wix APIs as a visitor |
| NLWeb | /_api/nlweb/ask?query=… |
A natural-language answer, written by a model, plus product results in Schema.org form |
NLWeb is an open project that gives a website one "ask" endpoint over its structured data. It's what Wix means when its pages mention NLWeb.
The three are separate. An agent built for UCP reads the profile and never sees the other two; a general assistant may find the site MCP server through llms.txt first. They're also built differently: UCP returns your catalog as data, while the NLWeb answer is generated text, so it reads more like your shop's chat assistant than a product feed. If you're testing how agents see your store, it's worth trying each one.
What isn't there yet
None of these stop an agent from browsing a Wix store, but they're what we'll be watching:
- Release 2026-04-08. Wix profiles still declare the April release; 2026-08-25 is current. An agent that only supports the newer release may not be able to negotiate with a Wix store until Wix moves.
- No order capability. Agents can't look up an order through UCP after the purchase.
- No signing keys. Wix profiles list no public keys, so messages from the store aren't signed. HTTPS still confirms the store's identity.
- Caching. The profile is served with
Cache-Control: max-age=60. The spec asks forpublicas well. It's a one-word difference, and only Wix can change it.
Since these all come from the platform, they'll change for every Wix store at once, the same way cart arrived on every Wix profile in October.
How to check your Wix store in UCP Checker
- Go to ucpchecker.com/check and type your domain, with or without
www. - Read the verdict at the top. A working Wix store shows Verified, with "Wix" as the platform, REST and MCP as transports, and release 2026-04-08. If it says Not found, your site may not be running Wix Stores, or the profile couldn't be reached.
- Read the findings. On a Wix store you'll typically see one problem, the caching header (marked as breaking the spec), and three to fix: no ETag, an older release, and no signing keys. All of them are set by Wix, not by you, so there's nothing to change in your dashboard.
- Check the note on payments. "Confirm checkout-link redirect strategy" means
payment_handlersis empty. For Wix this is expected: buyers pay on your checkout page. - Open the check trace. Under Calling its services you'll see the endpoints and the eight tools. Every request we made is listed, so you can see exactly what an agent sees.
Your store then has its own status page, which updates as we re-check it.
How to try it as an agent in UCP Playground
Checker reads what your store declares. UCP Playground lets you act on it, one call at a time:
- Open Inspect at ucpplayground.com/inspect.
- Pick your store. Open the store menu at the top left, choose Another store…, type your domain and press Enter. The Info panel shows the release, transports and capabilities it found.
- Choose the Store view and press Start. Playground connects over MCP and lists the store's tools in the trace on the right. If it says it found no profile, press Start again.
- Search. Type a product name and press Search. Your products appear as cards, built from the store's own answer.
- Add an item. On a Wix store this calls
create_checkout, since there's no cart tool, and the cart shows the item and the total. - Press Check out and open the newest
create_checkoutin the trace. Wix's reply is the handoff: statusrequires_escalation, the messagepayment_requires_site_checkout, and acontinue_urlto your checkout page. If a call comes back empty, press it again; every attempt stays in the trace. - Nothing is bought. Playground never completes a payment on a real store.
What a Wix merchant can control
The profile is Wix's. What you control is what agents find inside it:
- Product data. Titles, descriptions, variants, prices and stock are what an agent reads. Replace any sample products, and keep descriptions plain and factual.
- A working checkout page. The UCP handoff lands there, so make sure your store has one and that it accepts the buyer's country.
- Your domain. Agents find the profile on your domain. A custom domain, connected and redirecting cleanly, is what we check.
- Robots.txt. Don't block
/.well-known/ucp. Wix's default allows it. - Wix's own channels. If you're eligible, the Stripe and PayPal agentic options in Wix's Sales Channels are separate from the UCP profile and worth turning on too.
FAQ
Does my Wix store have a UCP profile?
Very likely. Wix publishes one for the Wix sites we check, without any setup. Type your domain into UCP Checker to see yours.
Do I need an app to use UCP on Wix?
No. The profile and its endpoints come from Wix. Third-party apps exist, but you don't need one for a store to be discoverable by UCP agents.
Can an AI agent buy from my Wix store?
An agent can search your products and build a priced checkout. Payment then happens on your own Wix checkout page: the agent hands the buyer a link to finish. Agents can't pay inside a chat with a Wix store yet.
Is Wix on UCP or ACP?
Both, in different ways. Wix markets ACP, Stripe and PayPal as its agentic channels, and separately serves a UCP profile for its stores. They aren't competing switches; a store can be reachable through several.
Why does UCP Checker flag my Wix store's caching or release?
Those come from Wix's platform, not your settings. Every Wix store shows the same findings, and they'll clear for everyone when Wix updates its template.
What is NLWeb on my Wix site?
An open "ask" endpoint Wix adds at /_api/nlweb/ask. It answers questions about your site in plain language. It's separate from your UCP profile, which is what commerce agents use to search and check out.
Why does my Wix site have a UCP profile if it isn't a shop?
Wix publishes the profile for sites without products too. A search on such a site returns nothing, so agents have nothing to buy.
About UCP Checker
UCP Checker is the independent validation and observability layer for the Universal Commerce Protocol. We crawl, validate and grade every public UCP manifest we can find, run the merchant directory, the UCP Score, live adoption stats, the vertical guides and the authority-bound vendor map, and track the spec as it evolves so you don't have to — measured from two vantages (what a business declares, and what actually happens when an agent transacts), the same way for everyone, without picking winners.
Sources
- Wix Blog: Agentic commerce on Wix and how AI agents can sell your products, Wix, updated October 2026
- Wix Blog: How to get AI agents to buy from your online store, Wix, October 2026
- Wix Help Center: PayPal agentic commerce services, an overview, Wix
- UCP specification, release 2026-04-08, Universal Commerce Protocol
- UCP Checker: Wix platform page and the State of Agentic Commerce, October 2026
- Live checks of a sample of 16 Wix stores' UCP profiles and MCP endpoints, October 31, 2026
Related coverage: The Shopify UCP Guide · The WooCommerce UCP Guide · The BigCommerce UCP Guide · Common UCP Errors
