UCP Checker
Sign in Start monitoring
Back to status
primoliquors.com icon
UCP Score

UCP Score for primoliquors.com

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

✓Verified
A97/100
Analyzed Sep 29, 2026 · 1 recommendation ·Shopify · v2026-08-25 latest
97
/ 100
UCP Conformance Score
A

primoliquors.com publishes a conforming manifest with broad capability coverage.

Agent Discovery100
UCP Conformance92
Capability Coverage100
Working

Agent Discovery is solid (100/100).

Start Here

Publish keys at the manifest root

Verified

primoliquors.com publishes a valid UCP manifest, with minor schema warnings.

Latency
167ms
Version
2026-08-25
Robots.txt
Allowed ✅

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

Medium impact Medium effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(0)

High impact, high effort

  • No items
Incremental Gains(1)

Medium impact & effort

  • Publish keys at the manifest root
Consider Later(0)

Lower priority

  • No items

How you compare on Shopify

Response time benchmarked against 10,683 Shopifies we monitor.

fastShopify median 166msslow
Your store
167ms
Shopify percentile
Below median
Faster than 48% of Shopify stores
Cohort range
152–188ms
p25 to p75 (middle half)

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

1

Publish keys at the manifest root

Medium impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents check that checkout responses really came from you. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec expects a root-level "keys" list (the older "signing_keys" field is still accepted while stores move). Stores that hand the buyer a checkout link instead of taking payment through the agent can go without them for now.

Show fix

Generate an Ed25519 keypair, publish the public key as a JWK in a root-level "keys" array (the canonical field since spec PR #566; "signing_keys" is legacy). Rotate annually; keep "kid" stable across rotations of the same key.

{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "<base64url-encoded-public-key>",
      "kid": "key-2026-04",
      "alg": "EdDSA"
    }
  ],
  "ucp": { ... }
}
UCP_MISSING_SIGNING_KEYS

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran Sep 6, 2026. Transport and URL resolution rows may be stale. Run a fresh check to re-probe.
Agent Discovery3/8 passed

Can AI agents find your store and its UCP manifest?

  • HTTPSCore

    Manifest served over a secure connection.

    Manifest URL uses https://

    Why it matters

    Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.

  • UCP manifest reachableCore

    Manifest fetched OK from /.well-known/ucp.

    HTTP 200

    Why it matters

    Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.

  • AI bot accessCore

    robots.txt allows agent crawlers to fetch the manifest.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.

  • llms.txtExperimental

    Hand-written brief at /llms.txt for AI agents.

    Not assessed: HTTP 429 (rate limited) on this check

    Why it matters

    Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.

  • sitemap.xmlCore

    XML sitemap published at /sitemap.xml.

    Not assessed: HTTP 429 (rate limited) on this check

    Why it matters

    Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.

  • Open Graph tagsCore

    OG meta tags on the homepage.

    Not assessed: HTTP 429 (rate limited) on this check

    Why it matters

    OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.

  • Organization schema (JSON-LD)Core

    Schema.org Organization (or OnlineStore) JSON-LD on homepage.

    Not assessed: HTTP 429 (rate limited) on this check

    Why it matters

    Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.

  • Mobile viewport metaCore

    Viewport meta tag for mobile rendering.

    Not assessed: HTTP 429 (rate limited) on this check

    Why it matters

    Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance3/5 passed

Does your manifest meet the published spec?

  • Manifest passes schema validationCore

    Manifest structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject manifests with structural errors. The error code in the diagnostic shows which field failed.

  • Protocol version present and well-formedCore

    ucp.version follows YYYY-MM-DD format.

    Version: 2026-08-25

    Why it matters

    UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.

  • Signing keys publishedCore

    Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.

    No signing_keys at root (common for managed/redirect-checkout stores)

    Why it matters

    Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.

  • No validation warningsCore

    Manifest passes structural and field-level rules.

    No outstanding validation issues

    Why it matters

    Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.

  • Spec & schema URLs resolve (25)Core

    Resolves the spec/schema URLs declared across the manifest to confirm agents can fetch each one.

    Not assessed: our requests to these 25 URLs did not connect on this check (a timeout on our side, not an answer from them). Left out of the score; we retry on the next check.

    Why it matters

    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.

Capability Coverage5/5 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    5 capabilities detected

    Why it matters

    Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.

  • Checkout capabilityCore

    Store declares a checkout-namespaced capability.

    dev.ucp.shopping.checkout detected

    Why it matters

    Without a checkout capability, agents can browse but can't complete a purchase end-to-end.

  • Transports declaredInterop

    Service transports (REST/MCP/A2A/Embedded) declared on services.

    MCP, EMBEDDED

    Why it matters

    Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.

  • Payment handlersCore

    Tokenized payment handlers registered for in-conversation checkout.

    3 handlers registered

    Why it matters

    Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.

  • MCP transport reachableInterop

    Live reachability check against https://primolfw.myshopify.com/api/ucp/mcp.

    tools/list returned a JSON-RPC response in 865ms

    Why it matters

    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.

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Order Management ✓ Bound 2026-08-25
Checkout ✓ Bound 2026-08-25
Discount Extension ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Identity Linking ✓ Bound 2026-08-25
Catalog Lookup ✓ Bound 2026-08-25
Catalog Search ✓ Bound 2026-08-25
Dev Shopify Catalog Extension ✓ Bound 2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://primoliquors.com/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports MCP, EMBEDDED
Last Observed
Last Full Index

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

UCP Score for primoliquors.com badge for https://ucpchecker.com/score/primoliquors.comLive preview
Markdown
[![UCP Score for primoliquors.com](https://ucpchecker.com/score/primoliquors.com/badge.svg)](https://ucpchecker.com/score/primoliquors.com)
HTML
<a href="https://ucpchecker.com/score/primoliquors.com"><img src="https://ucpchecker.com/score/primoliquors.com/badge.svg" alt="UCP Score for primoliquors.com"></a>
New · Early access open
Is primoliquors.com yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

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.

Save this report

Track primoliquors.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.