UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
magenxcommerce.com publishes a conforming profile with broad capability coverage.
UCP Conformance is solid (100/100).
Repair declared transport endpoints: One or more declared transport endpoints did not respond when probed.
Repair declared transport endpoints → Publish Organization schema (JSON-LD) on the homepage → Add Open Graph meta tags to the homepage
One or more declared transport endpoints did not respond when probed.
No Organization-typed JSON-LD detected on your homepage.
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 132 Customs we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more declared transport endpoints did not respond when probed.
A declared endpoint that does not answer stops an agent at that step, even though the profile itself validates. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.
No Organization-typed JSON-LD detected on your homepage.
Organization schema gives agents a structured representation of your brand identity: name, logo, social profiles, contact info, founding date. Agents use this to verify you are who you claim to be and to link your profile data to a recognizable entity.
Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "OnlineStore",
"name": "Yourstore",
"url": "https://yourstore.com",
"logo": "https://yourstore.com/logo.png",
"sameAs": [
"https://twitter.com/yourstore",
"https://www.instagram.com/yourstore"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-800-000-0000",
"contactType": "Customer Service"
}
}
</script>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">No viewport meta tag detected on your homepage.
Mobile-originating agent sessions (ChatGPT iOS, Apple Intelligence) render store pages in browser sandboxes that respect the viewport tag. Without it, the page renders at desktop width and pinch-to-zoom UX kicks in, and agents that take screenshots of pages get unreadable images.
One line inside <head>. Modern frontend frameworks add this automatically; its absence usually means a hand-rolled or legacy template.
<meta name="viewport" content="width=device-width, initial-scale=1">Every signal we evaluate, grouped by category.
Can AI agents find your store and its UCP profile?
Profile served over a secure connection.
Profile URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Profile 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 profile.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published profile 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.
Missing or incomplete on homepage
Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.
Viewport meta tag for mobile rendering.
Missing or incomplete on homepage
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your profile meet the published spec?
Profile structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject profiles 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.
Profile passes structural and field-level rules.
No outstanding validation issues
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 20 spec/schema URLs declared across the profile to confirm agents can fetch each one.
All 20 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 of 6 capability families detected: Checkout, Cart Management, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.
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.
REST, 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.
1 handler registered
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://www.magenxcommerce.com/api/ucp.
Reachable in 686ms (HTTP 200)
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
Live reachability check against https://www.magenxcommerce.com/api/ucp/mcp.
HTTP 400 on tools/list
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# Magenx Commerce
> Magenx Commerce — Premium Shopping Experience. A headless storefront on top
> of Magento (Adobe Commerce), available in fr, de, en, es, ar.
Pages are served under a locale path prefix (default: `/en`). Replace
`/en/` with any supported locale to reach its localized version.
Product detail pages live at `/en/product/<url-key>` and category
listing pages at `/en/category/<path>`, generated from the Magento
catalog. Full-text search is at `/en/search`.
## Shopping
- [Home](https://www.magenxcommerce.com/en): Featured products, best sellers, new arrivals and promotions.
- [Best Sellers](https://www.magenxcommerce.com/en/best-sellers)
- [Brands](https://www.magenxcommerce.com/en/brands): Browse products by manufacturer / brand.
- [Deals](https://www.magenxcommerce.com/en/deals): Current discounts and special offers.
- [Services](https://www.magenxcommerce.com/en/services): Available store services.
- [Blog](https://www.magenxcommerce.com/en/blog): Articles, buying guides and product news.
- [Contact](https://www.magenxcommerce.com/en/contact): Get in touch with the store.
## Account & Orders
- [Account](https://www.magenxcommerce.com/en/account): Sign-in, profile, addresses, orders, wishlist, returns, subscriptions and product alerts.
- [Cart](https://www.magenxcommerce.com/en/cart): Shopping cart.
- [Checkout](https://www.magenxcommerce.com/en/checkout): Place an order.
## Legal & Info
- [Privacy Policy](https://www.magenxcommerce.com/en/privacy-policy): Privacy policy.
- [Terms of Use](https://www.magenxcommerce.com/en/terms-of-use): Terms of use.
- [Legal](https://www.magenxcommerce.com/en/legal): Legal information.
- [Check Order](https://www.magenxcommerce.com/en/guest/order): Look up a guest order and request a return by order number + email.
- [Withdraw from the contract here](https://www.magenxcommerce.com/en/withdrawal): Right of withdrawal: declare withdrawal from a purchase.| Cart ✓ Bound | 2026-08-25 |
| Discount Extension ✓ Bound | 2026-08-25 |
| Order Management ✓ Bound | 2026-08-25 |
| Checkout ✓ Bound | 2026-08-25 |
| Fulfillment Extension ✓ Bound | 2026-08-25 |
| Catalog Lookup ✓ Bound | 2026-08-25 |
| Catalog Search ✓ Bound | 2026-08-25 |
| UCP Status | Verified |
| Endpoint | https://magenxcommerce.com/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-08-25 |
| Transports | REST, 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/magenxcommerce.com)<a href="https://ucpchecker.com/score/magenxcommerce.com"><img src="https://ucpchecker.com/score/magenxcommerce.com/badge.svg" alt="UCP Score for magenxcommerce.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 magenxcommerce.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.