UCP Score
UCP Score for denishenry.cz
84 out of 100, grade B: nearly there. The missing 16 points are spread across Discovery and Conformance and Capabilities. One spec break on the status page isn't counted in the score.
Discovery 95Conformance 91Capabilities 65release 2026-08-25
UCP Score
84/100
grade B · nearly there
Points missing→
16
Discovery, Conformance, Capabilities
Fixes→
3
raise the score
Spec breaks→
1
not in the score
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).
95−1.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.
91−3.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.
65−10.5 pts
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready
+11
Capabilities · effort medium
1Make declared services answer with UCP
One or more declared service endpoints did not give a UCP answer 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.
+2
Discovery · effort low
2Fill in your /llms.txt brand brief
Your /llms.txt answers, but the file is empty.
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.
# 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.
+4
Conformance · effort medium
3Cryptographic message signing is not yet enabled
Your UCP profile lists no public keys, so cryptographic message signing is not yet enabled for this store. HTTPS already confirms your store's identity; signing adds a further layer for checkout, payment and webhook messages.
The UCP spec recommends signing checkout completion and payment responses, and requires it for webhooks. A store that sends order updates by webhook needs keys; others can add them later.
{
"keys": [
{
"kty": "EC",
"crv": "P-256",
"x": "<base64url x>",
"y": "<base64url y>",
"kid": "store-2026-10",
"use": "sig",
"alg": "ES256"
}
],
"ucp": { ... }
}
Create a P-256 (ES256) key pair: ES256 is the one algorithm every UCP agent must be able to check. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, with its own "kid", and keep the private key on your server. The spec recommends a new key every 90 days: publish the new one next to the old, sign with it, and remove the old key a week later.
Agent Discovery · 7 of 8
7 OK
HTTPS, UCP profile reachable, AI bot access, sitemap.xml, Open Graph tags, Organization schema (JSON-LD), Mobile viewport metaShow
- HTTPS · Profile URL uses https://
- UCP profile reachable · HTTP 200
- AI bot access · robots.txt allows /.well-known/ucp
- sitemap.xml · Found at /sitemap.xml
- Open Graph tags · og:title and og:type/url present
- Organization schema (JSON-LD) · Organization-typed JSON-LD detected
- Mobile viewport meta · <meta name="viewport"> present
UCP Conformance · 3 of 5
3 OK
Profile passes schema validation, Protocol version present and well-formed, Spec & schema URLs resolve (12)Show
- Profile passes schema validation · No structural errors
- Protocol version present and well-formed · Version: 2026-08-25
- Spec & schema URLs resolve (12) · All 12 URLs resolved.
To fix
Conformance
No validation warnings
1 warning.
Capability Coverage · 3 of 5
3 OK
Capabilities declared, Checkout capability, Transports declaredShow
- Capabilities declared · 3 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.
- Checkout capability · dev.ucp.shopping.checkout detected
- Transports declared · REST
To fix
Capabilities
Payment handlers
Empty array: checkout-link redirect strategy.
Problem
Capabilities
REST transport reachable
HTTP 301.
The score measures what the profile declares across the three areas above. These break a rule in the spec that agents follow, so they can stop an agent before the score matters.
Speed among Shoptet stores
The profile answered in 150 ms, faster than 52% of the Shoptet stores we check.
