Your UCP manifest passes JSON.parse(). Your CI is green.
Google AI Mode hits /.well-known/ucp and moves on.
We just shipped a GitHub Action that catches this before merge:
github.com/Nolpak14/ucp-vali…
Valid JSON is not valid UCP.
Your manifest parses fine. Google AI Mode still skips your store.
10 checks that actually break AI agent discovery (with rule IDs and fixes):
Most articles about UCP's new Cart, Catalog, and Identity Linking capabilities have the spec details wrong.
We verified against the actual UCP GitHub repo. Two things almost everyone gets wrong:
Google just added 3 capabilities to UCP.
But 2 are draft specs and 1 is stable.
If your validator treats them the same, you're doing it wrong.
Here's why it matters:
70% of consumers use AI for shopping. AI bot traffic up 4x since Jan 2025.
Is your store ready? Here's the 7-item checklist:
1. UCP Profile
2. ACP Listing
3. Clean Product Data
4. Schema Markup
5. AI Traffic Monitoring
6. Validated Checkout
7. Agent-Readable Policies
UCP vs ACP - which AI shopping protocol do you need? Both!
UCP (Google + Shopify) = AI agents discover your store
ACP (OpenAI + Stripe) = ChatGPT buys from your store
Full breakdown in 8 minutes. Free readiness check at ucptools.dev
#UCP #ACP #ecommerce
This week we launched the first agentic commerce analytics platform.
5-stage funnel. 6 new KPIs. Per-agent conversion tracking.
AI agents are starting to make purchases via API calls.
GA4 can't see them. Mixpanel can't see them. Amplitude can't see them.
We built a demo to show what this blind spot looks like - and the numbers are wild.
Which AI shopping agent converts best?
We built an analytics dashboard that tracks per-agent performance. Here's what it looks like with sample data for a mid-size store:
@GeminiApp , @ChatGPTapp , @claudeai , @perplexity_ai , @Copilot - all compared.








