UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
fazy.com is conforming and ready for agent discovery and checkout.
UCP Conformance is solid (97/100).
Add endpoint URL to the service — Service uses a transport that requires an endpoint URL but none is declared.
Add endpoint URL to the service → Confirm checkout-link redirect strategy → Add Open Graph meta tags to the homepage
Service uses a transport that requires an endpoint URL but none is declared.
payment_handlers is present but empty.
OG tags missing or incomplete on your homepage.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 10,565 Shopifies we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
Service uses a transport that requires an endpoint URL but none is declared.
REST, MCP, and A2A transports all need a URL to call. Embedded is the only transport that omits this.
"endpoint": "https://yourstore.com/api/ucp/mcp"payment_handlers is present but empty.
An empty payment_handlers array tells agents "I do not tokenize — redirect the buyer to my hosted checkout instead." Common and valid for WooCommerce stores. Only an issue if you intended to support tokenized payment.
OG tags missing or incomplete on your homepage.
OG tags give agents and link unfurlers (Slack, iMessage, ChatGPT) a clean title, description, and image to represent your store. Without them, shares show garbled fallback text.
Add inside <head>. og:title and og:type are the minimum; og:url, og:description, and og:image are strongly recommended.
<meta property="og:title" content="Yourstore — short tagline">
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourstore.com/">
<meta property="og:description" content="One-sentence description of what you sell.">
<meta property="og:image" content="https://yourstore.com/og-cover.jpg">
<meta property="og:site_name" content="Yourstore">Every signal we evaluate, grouped by category.
Can AI agents find your store and its UCP manifest?
Manifest served over a secure connection.
Manifest URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Manifest fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the manifest.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
Found at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
Missing or incomplete on homepage
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your manifest meet the published spec?
Manifest structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject manifests with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-08-25
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.
signing_keys present
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Manifest passes structural and field-level rules.
2 warnings
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 14 spec/schema URLs declared across the manifest to confirm agents can fetch each one.
All 14 URLs resolved.
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
4 capabilities detected
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
Empty array — checkout-link redirect strategy
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# Fazy
> Fazy is a price-checked deals catalogue for US shoppers, rebuilt daily from live retailer inventory across home, wellness, apparel, footwear and electronics. Every listing carries the current price, the retailer's own reference price and a verified discount, and is retired the moment a link or price breaks. Fazy is not the seller: it hands the shopper to the retailer's checkout.
## For agents
- Search (JSON): https://fazy.com/api/v1/deals/search?q=standing+desk — free, keyless, 60/min per address
- One deal: https://fazy.com/api/v1/deals/{id}
- OpenAPI: https://fazy.com/api/v1/openapi.json
- MCP (Streamable HTTP, read-only, three tools): POST https://fazy.com/mcp
- Docs: https://fazy.com/developers
Send `X-Fazy-Agent: <your-agent-name>` and give shoppers the `url` field unchanged: it redirects to the retailer and attributes the click to you.
## For readers and crawlers
- Buying guides: https://fazy.com/best
- Categories: https://fazy.com/category/home · /wellness · /apparel · /footwear · /electronics · /appliances · /cosmetics
- Sitemap: https://fazy.com/sitemap.xml
- Editorial standards: https://fazy.com/editorial-standards| Cart ✓ Bound | 2026-08-25 |
| Order Management ✓ Bound | 2026-08-25 |
| Checkout | 2026-08-25 |
| Discount Extension | 2026-08-25 |
| Fulfillment Extension | 2026-08-25 |
| Buyer Consent Extension | 2026-08-25 |
| Catalog Lookup ✓ Bound | 2026-08-25 |
| Dev Shopify Catalog Extension ✓ Bound | 2026-08-25 |
| Dev Shopify Catalog Global Extension ✓ Bound | 2026-08-25 |
| Catalog Search ✓ Bound | 2026-08-25 |
| UCP Status | Verified |
| Endpoint | https://fazy.com/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-08-25 |
| Transports | MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/fazy.com)<a href="https://ucpchecker.com/score/fazy.com"><img src="https://ucpchecker.com/score/fazy.com/badge.svg" alt="UCP Score for fazy.com"></a>This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.
Track fazy.com's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.
Free. One email when something changes — no marketing. Privacy.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.