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

UCP Score for supremeco.boutir.com

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

✓Verified
A91/100
Analyzed Sep 28, 2026 · 4 recommendations ·Boutir · v2026-08-25 latest
91
/ 100
UCP Conformance Score
A

supremeco.boutir.com publishes a conforming manifest with broad capability coverage.

Agent Discovery85
UCP Conformance93
Capability Coverage95
Working

Capability Coverage is solid (95/100).

Start Here

Publish keys at the manifest root → Publish Organization schema (JSON-LD) on the homepage → Add Open Graph meta tags to the homepage

Verified

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

Latency
1,820ms
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
2
Publish Organization schema (JSON-LD) on the homepage

No Organization-typed JSON-LD detected on your homepage.

Medium impact Medium effort
3
Add Open Graph meta tags to the homepage

OG tags missing or incomplete on your homepage.

Low impact Low 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(2)

Medium impact & effort

  • Publish keys at the manifest root
  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(2)

Lower priority

  • Add Open Graph meta tags to the homepage
  • Add a mobile viewport meta tag

How you compare on Boutir

Response time benchmarked against 21 Boutirs we monitor.

fastBoutir median 501msslow
Your store
1820ms
Boutir percentile
Bottom quartile
Faster than 0% of Boutir stores
Cohort range
416–743ms
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
2

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

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 manifest data to a recognizable entity.

Show fix

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

<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>
UCP_MISSING_ORG_SCHEMA
3

Add Open Graph meta tags to the homepage

Low impact Low effort

OG tags missing or incomplete on your homepage.

Why it matters

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.

Show fix

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

<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">
UCP_MISSING_OG_TAGS
4

Add a mobile viewport meta tag

Low impact Low effort

No viewport meta tag detected on your homepage.

Why it matters

Mobile-originating agent sessions (ChatGPT iOS, Apple Intelligence) render store pages in browser sandboxes that respect the viewport tag. Without it, the page renders at desktop width and pinch-to-zoom UX kicks in, and agents that take screenshots of pages get unreadable images.

Show fix

One line inside <head>. Modern frontend frameworks add this automatically; its absence usually means a hand-rolled or legacy template.

<meta name="viewport" content="width=device-width, initial-scale=1">
UCP_MISSING_VIEWPORT

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran .
Agent Discovery5/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.

    Found at /llms.txt

    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.

    Found at /sitemap.xml

    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.

    Missing or incomplete on homepage

    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.

    Missing or incomplete on homepage

    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.

    Missing or incomplete on homepage

    Why it matters

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

UCP Conformance4/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 (17)Core

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

    All 17 URLs resolved.

    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 Coverage6/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    3 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.

    REST, MCP

    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.

    1 handler 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.

  • REST transport reachableInterop

    Live reachability check against https://supremeco.com.hk/apis/ucp.

    Reachable in 467ms (HTTP 200)

    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.

  • MCP transport reachableInterop

    Live reachability check against https://supremeco.com.hk/apis/ucp/mcp.

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

    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.

/llms.txt content

The plain-text brief this store publishes to AI agents. Captured on the most recent check.

1.7 KBcf30b13b49809f97
mentions UCP
# llms.txt
# Public brief for AI agents about 香港永高行網店

# About
永高行始創於1987年，由一間小型求生用品店，擴充成為進口商, 批發商和零售商。是行內歷史最悠久的戶外裝備用品零售商之一。

從九十年代起，本公司已不斷引進多個戶外裝備品牌到亞洲市場。本公司代理行業內頂級的品牌，進口及批發至亞洲多個地區。我們不僅是一間貿易公司，我們對品牌熱誠推廣也參與投入產品開發，也與供應商和經銷商建立良好的關係。與此同時，我們極力推廣安全射擊運動，積極贊助多項射擊活動。近年更積極拓展戶外裝備用品。給客人帶來更多選擇。

另外，我們獲得多個優質服務零售商感到榮幸，繼續為大家提供優質產品和服務。

2023年 永高行改名為 永高行戶外有限公司經營業務

# Product Categories
- Mystery Ranch
- Mystery Ranch > 單肩包
- Mystery Ranch > 女款 women
- Mystery Ranch > 徒步重裝背包
- Mystery Ranch > 收納袋
- Mystery Ranch > 旅行包袋
- Mystery Ranch > 日常、城市通勤包
- Mystery Ranch > 男款 Men
- Mystery Ranch > 章及帽
- Mystery Ranch > 美國製
- Mystery Ranch > 背包配件
- Mystery Ranch > 腰包系列
- 品牌分類
- 品牌分類 > A－D
- 品牌分類 > A－D > AKU
- 品牌分類 > A－D > Acebeam
- 品牌分類 > A－D > Amvel Verykal
- 品牌分類 > A－D > Arc'teryx
- 品牌分類 > A－D > Ballistic Industries
- 品牌分類 > A－D > Barebones

# Policies
- Return policy: https://supremeco.boutir.com/returnpolicy
- Terms: https://supremeco.com.hk/p/Refund_Returns
- Privacy: https://supremeco.com.hk/p/Privacy

# UCP
- Discovery profile: https://supremeco.boutir.com/.well-known/ucp
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Discount Extension ✓ Bound 2026-08-25
Checkout ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Catalog Lookup ✓ Bound 2026-08-25
Catalog Search ✓ Bound 2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://supremeco.boutir.com/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports REST, MCP
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 supremeco.boutir.com badge for https://ucpchecker.com/score/supremeco.boutir.comLive preview
Markdown
[![UCP Score for supremeco.boutir.com](https://ucpchecker.com/score/supremeco.boutir.com/badge.svg)](https://ucpchecker.com/score/supremeco.boutir.com)
HTML
<a href="https://ucpchecker.com/score/supremeco.boutir.com"><img src="https://ucpchecker.com/score/supremeco.boutir.com/badge.svg" alt="UCP Score for supremeco.boutir.com"></a>
New · Early access open
Is supremeco.boutir.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 supremeco.boutir.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.