UCP Checker
Back to status
claw-bounty.com icon
UCP Score

UCP Score for claw-bounty.com

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

✓Verified
A95/100
Analyzed Oct 11, 2026 · 4 recommendations ·Salla · v2026-04-08 upgrade
95
/ 100
UCP Score
A

claw-bounty.com publishes a conforming profile with broad capability coverage.

Agent Discovery100
UCP Conformance88
Capability Coverage100
Working

Agent Discovery is solid (100/100).

Start Here

Name capabilities the way the spec does → Name payment handlers the way the spec does → Use YYYY-MM-DD for handler version

Verified

claw-bounty.com publishes a valid UCP profile, with minor schema warnings.

Latency
935ms
Version
2026-04-08
Robots.txt
Allowed ✅

Top Priorities

1
Name capabilities the way the spec does

A capability is not named in the spec's dotted form (e.g. dev.ucp.shopping.checkout).

Medium impact Low effort
2
Name payment handlers the way the spec does

A payment handler is not named in the spec's dotted form (e.g. com.google.pay).

Medium impact Low effort
3
Use YYYY-MM-DD for handler version

A payment handler version is not in YYYY-MM-DD format.

Medium 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(3)

Medium impact & effort

  • Name capabilities the way the spec does
  • Name payment handlers the way the spec does
  • Use YYYY-MM-DD for handler version
Consider Later(1)

Lower priority

  • Move to the latest UCP protocol version

How you compare on Salla

Response time benchmarked against 110 Sallas we monitor.

fastSalla median 650msslow
Your store
935ms
Salla percentile
Bottom quartile
Faster than 6% of Salla stores
Cohort range
525–757ms
p25 to p75 (middle half)

Recommendations

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

1

Name capabilities the way the spec does

Medium impact Low effort ×9

A capability is not named in the spec's dotted form (e.g. dev.ucp.shopping.checkout).

Why it matters

Capabilities are named like reversed web addresses so that names never collide: "checkout" is ambiguous; "dev.ucp.shopping.checkout" is not.

Show fix
"capabilities": {
  "dev.ucp.shopping.checkout": [...]
}
UCP_CAPABILITY_INVALID_KEY
2

Name payment handlers the way the spec does

Medium impact Low effort

A payment handler is not named in the spec's dotted form (e.g. com.google.pay).

Why it matters

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.

Show fix
"payment_handlers": {
  "com.google.pay": [...]
}
UCP_HANDLER_INVALID_KEY
3

Use YYYY-MM-DD for handler version

Medium impact Low effort

A payment handler version is not in YYYY-MM-DD format.

Why it matters

Handler versions follow the same date-based format as everything else in UCP.

Show fix
"version": "2026-08-25"
UCP_HANDLER_INVALID_VERSION
4

Move to the latest UCP protocol version

Low impact Low effort

Your profile declares a valid but older protocol version. A newer one is published.

Why it matters

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.

Show fix

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 it
UCP_VERSION_OUTDATED

Full Check Breakdown

Every signal we evaluate, grouped by category.

Agent Discovery8/8 passed

Can AI agents find your store and its UCP profile?

  • HTTPSCore

    Profile served over a secure connection.

    Profile 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 profile reachableCore

    Profile 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 profile.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published profile 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.

    og:title and og:type/url present

    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.

    Organization-typed JSON-LD detected

    Why it matters

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

  • Mobile viewport metaCore

    Viewport meta tag for mobile rendering.

    <meta name="viewport"> present

    Why it matters

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

UCP Conformance3/4 passed

Does your profile meet the published spec?

  • Profile passes schema validationCore

    Profile structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject profiles 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-04-08

    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.

    signing_keys present

    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

    Profile passes structural and field-level rules.

    11 warnings

    Why it matters

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

Capability Coverage3/4 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    5 of 6 capability families detected: Checkout, Identity Linking, Cart Management, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.

    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 declared, not named the way the spec expects (e.g. com.google.pay), so agents cannot look it up

    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.

/llms.txt content

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

7.2 KBa701e0f100f50921
mentions UCP
# متجر كلاو باونتي راش

> متجر كلاو باونتي راش هو منصة متخصصة في بيع حسابات لعبة "ون بيس باونتي راش" (One Piece Bounty Rush)، حيث يوفر حسابات إكستريم (EX) نادرة، وحسابات مشحونة بآلاف الجواهر والأحجار الذهبية. يستهدف المتجر اللاعبين الراغبين في الحصول على بداية قوية أو شخصيات مطورة بالكامل (Max) دون الحاجة لقضاء وقت طويل في التجميع اليدوي. يتميز المتجر بنظام تسليم فوري وآلي للحسابات فور إتمام عملية الشراء لضمان سرعة الخدمة.
>
> تتراوح أسعار الحسابات بين 120 ريال سعودي للحسابات المتوسطة وتصل إلى 2500 ريال سعودي للحسابات الأسطورية التي تضم أكثر من 20 شخصية إكستريم وتطويرات متقدمة. جميع المنتجات رقمية ويتم تسليم بيانات الدخول مباشرة للمشتري، مع توفير حسابات مخصصة لكل من منصتي الأندرويد والآيفون لضمان توافق رصيد الجواهر.
- WhatsApp: +966554846590


## Supported Languages

- العربية (rtl)

## Product Categories

- [حسابات قوية بسعر رخيص!](https://claw-bounty.com/category/YDGaAn): حسابات باونتي راش اقتصادية للمبتدئين بمواصفات جيدة وأسعار تنافسية
- [حسابات جواهر للايفون](https://claw-bounty.com/category/VaZOXE): حسابات مشحونة بكميات كبيرة من الجواهر مخصصة لمستخدمي نظام iOS
- [حسابات جواهر للاندرويد](https://claw-bounty.com/category/NpgBRn): حسابات تحتوي على رصيد جواهر مرتفع مخصصة لمستخدمي نظام الأندرويد
- [اكستريم ماكس وجواهر](https://claw-bounty.com/category/NrQwEb): حسابات تضم شخصيات إكستريم مطورة للمستوى 100 مع رصيد جواهر إضافي
- [حسابات فوق 10 اكستريم](https://claw-bounty.com/category/vZQXYE): حسابات نادرة تضم تشكيلة واسعة من شخصيات الإكستريم القوية للمحترفين
- [خدمات الحسابات](https://claw-bounty.com/category/REnOzY): خدمات متنوعة لتطوير وتحسين حسابات باونتي راش القائمة
- [تخفيضات](https://claw-bounty.com/offers): عروض خاصة وحسابات بأسعار مخفضة لفترة محدودة

## Top Products

- [اكستريم ساترن ماكس!](https://claw-bounty.com/ar/product-1705316934/p1705316934): حساب يضم شخصية ساترن مطورة للمستوى الأقصى جاهز للعب التنافسي، 500 SAR
- [5000/6000+ جوهرة واكستريم ساترن للاندرويد](https://claw-bounty.com/ar/product-536133946/p536133946): حساب أندرويد يحتوي على أكثر من 5000 جوهرة مع شخصية ساترن، 400 SAR
- [5000/6000+ جوهرة واكستريم ساترن للايفون](https://claw-bounty.com/ar/product-1462164662/p1462164662): حساب آيفون يحتوي على أكثر من 5000 جوهرة مع شخصية ساترن، 400 SAR
- [5000/5500+ جوهرة واكستريم ساترن وجوي بوي الرنر للايفون](https://claw-bounty.com/ar/product-500634626/p500634626): حساب آيفون يجمع بين شخصيات الميتا القوية ورصيد ضخم من الجواهر، 900 SAR
- [5000/5500+ جوهرة واكستريم ساترن ولوتشي واكاينو للايفون](https://claw-bounty.com/ar/product-580963864/p580963864): حساب آيفون يضم شخصيات إكستريم متنوعة مع رصيد جواهر مرتفع، 900 SAR
- [15 اكستريمات 10 ماكس وشانكس فل هايبر](https://claw-bounty.com/ar/product-1995836701/p1995836701): حساب أسطوري بـ 15 شخصية إكستريم وتطويرات هايبر بوست متقدمة، 2500 SAR
- [20 اكستريمات وفيه ساترن ومشحون سكن اكاينو](https://claw-bounty.com/ar/product-413776961/p413776961): حساب متكامل يضم 20 شخصية إكستريم وسكنات حصرية نادرة، 2500 SAR
- [12 اكستريمات ميتا وفيه ساترن](https://claw-bounty.com/ar/product-1320887920/p1320887920): حساب يضم 12 شخصية إكستريم من شخصيات الميتا الحالية، 650 SAR
- [10 اكستريمات ميتا 8 ماكسات وفيه ساترن](https://claw-bounty.com/ar/product-415585505/p415585505): حساب يضم 10 شخصيات إكستريم مع سكنات حصرية مشحونة، 850 SAR
- [9 اكستريمات ميتا وساترن و1142 جوهرة اندرويد](https://claw-bounty.com/ar/product-1895189831/p1895189831): حساب أندرويد يجمع بين شخصيات الإكستريم ورصيد جواهر جاهز للسحب، 450 SAR
- [اوكيجي ماكس وساترن وروجر الرنر](https://claw-bounty.com/ar/product-25429910/p25429910): حساب اقتصادي يضم ثلاث شخصيات إكستريم قوية مطورة، 120 SAR
- [13 اكستريمات 7 ماكس وفيه ساترن](https://claw-bounty.com/ar/product-1466294307/p1466294307): حساب متطور يضم 13 شخصية إكستريم مع 7 شخصيات بمستوى ماكس، 890 SAR
- [9 اكستريمات 4 ماكسات وسولو هارد جديد](https://claw-bounty.com/ar/product-1724089206/p1724089206): حساب يضم 9 شخصيات إكستريم مع إمكانية تجميع جواهر إضافية من السولو، 300 SAR
- [7 اكستريمات 4 ماكسات](https://claw-bounty.com/ar/product-380286816/p380286816): حساب متوازن يضم 7 شخصيات إكستريم بأسعار متوسطة، 250 SAR
- [4 اكستريمات 3 ماكس وساترن](https://claw-bounty.com/ar/product-2137553429/p2137553429): حساب يركز على شخصيات إكستريم محددة مطورة للمستوى الأقصى، 275 SAR

## Support / FAQ

- [ماذا نقدم؟](https://claw-bounty.com/p/NpRWD): تفاصيل حول أنواع الحسابات والخدمات المتوفرة في المتجر
- [صفحة تعريفية عن المتجر](https://claw-bounty.com/p/pzOYX): معلومات حول متجر كلاو باونتي راش ورؤيته في خدمة اللاعبين

## Docs

- [API Catalog](https://claw-bounty.com/.well-known/api-catalog): Full list of available store API endpoints
- [MCP](https://claw-bounty.com/mcp): Model Context Protocol endpoint for AI tool integration
- [UCP](https://claw-bounty.com/.well-known/ucp): Universal Commerce Protocol discovery — agent-facing catalog search, cart, and checkout
- [Sitemap](https://claw-bounty.com/sitemap.xml): Complete sitemap of all store pages and products
- [Robots.txt](https://claw-bounty.com/robots.txt): Crawl and indexing directives for search engines
- [OAuth Discovery](https://claw-bounty.com/.well-known/openid-configuration): OAuth 2.0/OpenID Connect discovery endpoint

Any store page can be returned as markdown by sending `Accept: text/markdown` in the request headers.
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Checkout 2026-04-08
Cart 2026-04-08
Catalog Search 2026-04-08
Catalog Lookup 2026-04-08
Fulfillment 2026-04-08
Discount 2026-04-08
Buyer Consent 2026-04-08
Order Management 2026-04-08
Identity Linking 2026-04-08

Technical Vitals

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