UCP Checker
Check a store
UCP Score

UCP Score for oxid7-75-fb5k1r3a.patsy-dev.payone-office.de

Ready for UCP agents

93 out of 100, grade A: ready for UCP agents. The missing 7 points are spread across Discovery and Conformance and Capabilities.

Discovery 85Conformance 96Capabilities 97release 2026-08-25

UCP Score 93/100 grade A · ready for UCP agents
Points missing 7 Discovery, Conformance, Capabilities Fixes 4 raise the score

How the score is made

three areas, weighted
Discovery 30%
Can a UCP agent find and read the profile: HTTPS, an answer at /.well-known/ucp, robots.txt allowing it, and five files outside UCP (llms.txt, sitemap, Open Graph, Organization schema, viewport).
85−4.5 pts
Conformance 40%
Does the profile follow the spec: valid against its release (counted three times), a dated release, keys published, few warnings, spec and schema links that resolve.
96−1.6 pts
Capabilities 30%
What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.
97−0.9 pts
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready

Raise the score

fixes that move the number
+2
1Fix broken spec or schema URLs
One or more spec/schema URLs declared in the profile 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 profile setup. See the Full Check Breakdown for the specific URLs that failed.
Conformance · effort low
part of +5
2Publish Organization schema (JSON-LD) on the homepage
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.
Discovery · effort medium 
<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>

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

part of +5
3Publish a /llms.txt brand brief
No /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.
Discovery · effort low 
# 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 profile: /.well-known/ucp
- Supported flows: cart, checkout, tokenized payment, etc.
- Anything explicitly NOT supported (e.g. "no subscription products via agent")

# Contact
[email protected]

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.

part of +5
4Publish a sitemap.xml
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.
Discovery · effort low 
<?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>

Most ecommerce platforms generate sitemap.xml automatically. If yours does not, generate one and serve it at /sitemap.xml.

Every check

15 passed · 4 to fix
Agent Discovery · 5 of 8
5 OK
HTTPS, UCP profile reachable, AI bot access, Open Graph tags, Mobile viewport metaShow
  • HTTPS · Profile URL uses https://
  • UCP profile reachable · HTTP 200
  • AI bot access · robots.txt allows /.well-known/ucp
  • Open Graph tags · og:title and og:type/url present
  • Mobile viewport meta · <meta name="viewport"> present
Problem
llms.txt
HTTP 301 at /llms.txt. Fix 3 above.
Discovery
Problem
sitemap.xml
HTTP 301 at /sitemap.xml. Fix 4 above.
Discovery
Problem
Organization schema (JSON-LD)
Missing or incomplete on homepage. Fix 2 above.
Discovery
UCP Conformance · 4 of 5
4 OK
Profile passes schema validation, Protocol version present and well-formed, Public keys published, No validation warningsShow
  • Profile passes schema validation · No structural errors
  • Protocol version present and well-formed · Version: 2026-08-25
  • Public keys published · Keys published at the top level
  • No validation warnings · No outstanding validation issues
To fix
Spec & schema URLs resolve (15)
Did not resolve (3 of 15): https://ucp.dev/2026-08-25/schemas/shopping/catalog.json, https://ucp.dev/2026-08-25/specification/shopping/fulfillment/, https://ucp.dev/2026-08-25/specification/shopping/buyer-consent/.
Conformance
Capability Coverage · 6 of 6
6 OK
Capabilities declared, Checkout capability, Transports declared, Payment handlers, REST transport reachable, MCP transport reachableShow
  • Capabilities declared · 4 of 6 capability families detected: Checkout, Cart Management, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.
  • Checkout capability · dev.ucp.shopping.checkout detected
  • Transports declared · REST, MCP
  • Payment handlers · 2 handlers registered
  • REST transport reachable · Reachable in 286ms (HTTP 200)
  • MCP transport reachable · tools/list returned a JSON-RPC response in 274ms
Speed among Custom stores
The profile answered in 198 ms, faster than 78% of the Custom stores we check.