UCP Checker
Check a store
UCP Score

UCP Score for spoonfulofcomfort.com

Ready for UCP agents

91 out of 100, grade A: ready for UCP agents. The missing 9 points are spread across Discovery and Capabilities. One spec break on the status page isn't counted in the score.

Discovery 95Conformance 100Capabilities 75release 2026-04-08

UCP Score 91/100 grade A · ready for UCP agents
Points missing 9 Discovery, Capabilities Fixes 3 raise the score Spec breaks 1 not in 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).
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.
100full marks
Capabilities 30%
What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.
75−7.5 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
+8
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.
Capabilities · effort medium
To fix
2Move to the latest UCP protocol version
Your profile declares a valid but older protocol version. A newer one is published.
Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The profile itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.
Conformance · effort low 
"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // beside "ucp", not inside it

Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.

+2
3Add Open Graph meta tags to the homepage
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.
Discovery · effort low 
<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">

Add inside <head>. og:title and og:type are the minimum; og:url, og:description, and og:image are strongly recommended.

Every check

16 passed · 2 to fix
Agent Discovery · 7 of 8
7 OK
HTTPS, UCP profile reachable, AI bot access, llms.txt, sitemap.xml, 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
  • llms.txt · Found at /llms.txt
  • sitemap.xml · Found at /sitemap.xml
  • Organization schema (JSON-LD) · Organization-typed JSON-LD detected
  • Mobile viewport meta · <meta name="viewport"> present
Problem
Open Graph tags
Missing or incomplete on homepage. Fix 3 above.
Discovery
UCP Conformance · 5 of 5
5 OK
Profile passes schema validation, Protocol version present and well-formed, Public keys published, No validation warnings, Spec & schema URLs resolve (20)Show
  • Profile passes schema validation · No structural errors
  • Protocol version present and well-formed · Version: 2026-04-08
  • Public keys published · Keys published at the top level
  • No validation warnings · No outstanding validation issues
  • Spec & schema URLs resolve (20) · All 20 URLs resolved.
Capability Coverage · 4 of 5
4 OK
Capabilities declared, Checkout capability, Transports declared, Payment handlersShow
  • Capabilities declared · 3 of 6 capability families detected: Checkout, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.
  • Checkout capability · dev.ucp.shopping.checkout detected
  • Transports declared · REST
  • Payment handlers · 2 handlers registered
Problem
REST search_catalog
search_catalog did not return a UCP answer (HTTP 422).
Capabilities

Not in the score, but worth fixing first

spec breaks
To fix
The profile has no ETag or Last-Modified header
Spec level: SHOULD.
on the status page

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 Bigcommerce stores
The profile answered in 340 ms, faster than 60% of the Bigcommerce stores we check.