UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
Solid UCP setup on ucp.meetanshi.in with a few gaps left to close.
UCP Conformance is solid (89/100).
Repair declared transport endpoints — One or more declared transport endpoints did not respond when probed.
Repair declared transport endpoints → Fix broken spec or schema URLs → Publish Organization schema (JSON-LD) on the homepage
One or more declared transport endpoints did not respond when probed.
One or more spec/schema URLs declared in the manifest do not resolve.
No Organization-typed JSON-LD detected 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 5 Magentos we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more declared transport endpoints did not respond when probed.
A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.
One or more spec/schema URLs declared in the manifest do not resolve.
Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial manifest setup. See the Full Check Breakdown for the specific URLs 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 manifest 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>Your manifest declares a valid but older spec version. A newer published version is available.
Older versions stay valid (agents pin to the version you declare), but newer agent capabilities — embedded checkout, AP2 mandates, identity linking, 3DS payment authentication, payment terms and location lookup — only resolve against the latest spec. The manifest envelope barely moved: signing_keys went from inside ucp to the root as of 2026-04-08, and v2026-08-25 replaced it with keys (a JWK Set). Everything else in v2026-08-25 changed in the capability vocabulary, not the envelope.
Bump version to 2026-08-25 and publish your public keys as a root-level keys array (JWK Set). Legacy signing_keys is still accepted, at the root or nested, but keys is the canonical field every verifier reads. See /specs/2026-08-25 for the full release notes.
"ucp": {
"version": "2026-08-25",
...
},
"keys": [ ... ] // JWK Set, sibling of ucp, not nested insideNo /llms.txt file detected at the root of your domain.
llms.txt is an emerging convention (analogous to robots.txt) that lets you give AI agents a hand-written brief about your brand, product categories, return policy, and crawl preferences. Strict UCP agents do not require it, but recommendation/discovery agents increasingly read it for context.
Save as /llms.txt at your site root. Plain text, written for an LLM audience. The format is informal — these section headings are a working convention, not a spec. Replace the placeholders with your own brand details and update when policies or product lines change.
# llms.txt
# Public brief for AI agents about Yourstore
# About
One or two sentences on what you sell, who you sell to, and any defining context (founded, mission, sustainability stance, etc.).
# Product Categories
- Category one
- Category two
- Category three
# Policies
- Returns: e.g. 30 days, full refund
- Shipping: e.g. Free over $30, 3-5 business days
- Any other policy worth surfacing (cruelty-free, vegan, made-to-order, etc.)
# Agent Capabilities
- UCP manifest: /.well-known/ucp
- Supported flows: cart, checkout, tokenized payment, etc.
- Anything explicitly NOT supported (e.g. "no subscription products via agent")
# Contact
[email protected]No sitemap.xml detected at the root of your domain.
Sitemaps tell agents and crawlers which pages on your store are canonical and how often they change. Without one, agents fall back to following internal links, which is slower and less complete — especially for catalog pages buried behind faceted nav.
Most ecommerce platforms generate sitemap.xml automatically (Shopify, WooCommerce). If yours does not, generate one server-side and serve at /sitemap.xml.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://yourstore.com/</loc>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://yourstore.com/products</loc>
<changefreq>daily</changefreq>
</url>
<!-- one <url> entry per indexable page -->
</urlset>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.
HTTP 404 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.
HTTP 404 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 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-04-08
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.
No outstanding validation issues
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 30 spec/schema URLs declared across the manifest to confirm agents can fetch each one.
Did not resolve (16 of 30): https://ucp.dev/2026-04-08/services/shopping/openapi.json, https://ucp.dev/2026-04-08/specs/shopping/order, https://ucp.dev/2026-04-08/specification/catalog-search, https://ucp.dev/2026-04-08/specification/catalog-lookup, https://ucp.dev/2026-04-08/specification/catalog-product, …
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.
5 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.
REST
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://ucp.meetanshi.in/rest/V1/ucp.
HTTP 500
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 manifest itself looks perfect.
| Cart ✓ Bound | 2026-04-08 |
| Cart Note Extension ✓ Bound | 2026-04-08 |
| Cart Refresh Extension ✓ Bound | 2026-04-08 |
| Order Management ✓ Bound | 2026-04-08 |
| Policy ✓ Bound | 2026-04-08 |
| Checkout ✓ Bound | 2026-04-08 |
| Discount Extension ✓ Bound | 2026-04-08 |
| Gift Card Extension ✓ Bound | 2026-04-08 |
| Fulfillment Extension ✓ Bound | 2026-04-08 |
| Buyer Identity Extension ✓ Bound | 2026-04-08 |
| Catalog Lookup ✓ Bound | 2026-04-08 |
| Catalog Search ✓ Bound | 2026-04-08 |
| Catalog Product ✓ Bound | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://ucp.meetanshi.in/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | REST |
| 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/ucp.meetanshi.in)<a href="https://ucpchecker.com/score/ucp.meetanshi.in"><img src="https://ucpchecker.com/score/ucp.meetanshi.in/badge.svg" alt="UCP Score for ucp.meetanshi.in"></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 ucp.meetanshi.in'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.