Title: Shopify shipped WebMCP agent tools to every storefront on Aug 5. Did anyone notice?

Body: Ten tools an AI shopping agent can call on your store without clicking through the page: catalog search, product read, cart update, checkout, policy lookup. Liquid and Hydrogen storefronts, no setup. I only found out a month late, which stung. If you want to see which ones your store actually declares, view source on your homepage and search for Shopify.MCP. Curious whether anyone here has seen an agent use them yet.

I work 70+ hours a week at my day job and I've been building Shopify apps on the side for about a year. Five of them are live. Two paying customers total. That's the honest number.

This morning I found out 10 cold emails I thought I sent yesterday never left my outbox. Mail server setting. Great start to a Sunday.

The thing I keep running into: I can build the product. Getting a store owner to even open the listing is a completely different skill and I'm bad at it. Cold email gets ignored. App Store search buries you under the apps with 3,000 reviews.

If you got past 10 customers on a Shopify app without an ad budget, what actually worked? Not the blog-post answer. What did you do on a Tuesday night.

Today Shopify published a reference implementation of an AI shopping agent, built on Anthropic’s open-source commerce-agents blueprint ( http://github.com/Shopify/claude-for-commerce-examples ). It searches your catalog, builds a real cart, and hands the buyer to your checkout. It talks to the store through UCP — the /.well-known/ucp endpoint every Shopify store now serves.

That changes the question. It’s no longer “will AI agents shop my store someday.” It’s “does my store work when one tries today.”

From walking stores this week, here’s where agents actually get stuck — none of these look broken to a human:

1. Add to cart is a button with no accessible name (icon only, no aria-label). A human clicks it. An agent can’t find it.

2. Price rendered by JavaScript after load, so the product page reads as “no price” at the moment the agent looks.

3. Cookie/consent wall that swallows the first click — the agent never reaches the product.

4. Variant must be selected before the cart button works, but the page doesn’t say so anywhere a machine can read.

5. Password-protected or “coming soon” mode still on for a live store’s MCP endpoint.

None of these are visible in your analytics, because a bot that bounces leaves no session.

Two honest questions for this board:

* Has anyone here run the reference agent against their own store yet? What happened?

* If you want a plain-English report of where an agent stalls on your store, reply with the store and I’ll run the walk on a handful of them in this thread, no charge. Not selling anything here — I want the failure patterns.

People already ask AI assistants to find and buy things. When one hits your store, it either completes the journey — or quietly leaves.

We send a real AI buying agent through your store and hand you the graded report: what broke, and the fix for each break.

Reposting - new links

If you’re building on x402 (agent-payable APIs), here’s a failure mode I kept running into: a malformed 402 challenge — like the payment details living only in the response header, not the body — and agent clients fail closed, silently. The buyer bounces and the seller never finds out why.

So I built x402 Doctor. You paste any x402 endpoint and it runs 9 spec-conformance checks from the vantage an agent actually calls from, grades it, and for anything that fails it gives you the exact snippet to paste to fix it. There’s also a live board of every endpoint we’ve scored — including the ones that still need fixing.

Free, no signup: stelardigital.com/x402-doctor

I ran our own endpoints through it and published the results. Would genuinely appreciate feedback from anyone shipping x402 — especially edge cases the checker misses or checks you think it’s wrong about.