UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
Solid UCP setup on bareeqslv.com with a few gaps left to close.
Agent Discovery is solid (95/100).
Declare a transport on the service — Service entry has no "transport" field and no legacy nested transport.
Declare a transport on the service → Name services the way the spec does → Name payment handlers the way the spec does
Service entry has no "transport" field and no legacy nested transport.
A service is not named in the spec's dotted form (e.g. dev.ucp.shopping).
A payment handler is not named in the spec's dotted form (e.g. com.google.pay).
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 Zids we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
Service entry has no "transport" field and no legacy nested transport.
Without a transport, agents do not know whether to speak REST, MCP, or A2A to your endpoint.
Allowed transport values per spec: rest, mcp, a2a, embedded.
{
"version": "2026-08-25",
"transport": "mcp",
"endpoint": "https://yourstore.com/api/ucp/mcp"
}A service is not named in the spec's dotted form (e.g. dev.ucp.shopping).
Like capabilities, services are named like reversed web addresses so names never collide.
"services": {
"dev.ucp.shopping": [...]
}A payment handler is not named in the spec's dotted form (e.g. com.google.pay).
Handlers are named like reversed web addresses (com.google.pay, com.stripe.terminal) so every store declaring the same payment method names it the same way, and an agent can recognise it.
"payment_handlers": {
"com.google.pay": [...]
}A payment handler is missing the required "version" field.
Handler versions evolve independently of the manifest. Agents pin their token request format to a specific handler version.
"version": "2026-08-25"Your manifest 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 manifest 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.
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.
"ucp": {
"version": "2026-08-25",
...
},
"keys": [ ... ] // beside "ucp", not inside itNo /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]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.
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.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
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.
4 warnings
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
1 capability 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.
No checkout capability
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.
No transports declared
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 declared, not named the way the spec expects (e.g. com.google.pay), so agents cannot look it up
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
| Search | 2026-04-08 |
| Catalog | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://bareeqslv.com/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | — |
| 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/bareeqslv.com)<a href="https://ucpchecker.com/score/bareeqslv.com"><img src="https://ucpchecker.com/score/bareeqslv.com/badge.svg" alt="UCP Score for bareeqslv.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 bareeqslv.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.