What does it mean that cardial.sa is verified for UCP?

It means cardial.sa publishes a valid UCP manifest at /.well-known/ucp, the manifest passes schema validation against 2026-04-08, and AI agents can discover its commerce capabilities without needing to scrape HTML. That is what the store declares. Whether an agent actually completes a purchase is a separate question — where an observed agent run is shown on this page, it answers that one.

Can I trust cardial.sa for AI agent purchases?

Verification means the store is technically ready — payment handlers declared, transports reachable, schema valid. It doesn't grade business reputation or fulfilment quality. For trust on the commerce side itself, check the store's own reviews. For trust on the agent integration side, this page is the source of truth.

What platform does cardial.sa use for UCP?

Our detection identifies cardial.sa as running on Salla. Many large UCP-verified stores use Shopify, BigCommerce, or custom stacks built on the open spec. The transport list above shows the exact mechanism (REST, MCP, A2A, Embedded) the manifest declares.

How was this UCP report for cardial.sa generated?

Our crawler fetches cardial.sa/.well-known/ucp directly, parses the manifest against the official UCP JSON schema, checks robots.txt for AI bot policies, and runs payment-handler validation. No manual review, no opinions — just what the manifest actually says. The check ran 2 hours ago.

How often is cardial.sa re-checked?

Every domain in our directory is re-crawled at least every 24 hours. You can also trigger a fresh check from this page at any time, or subscribe to alerts to get notified the moment the status changes — that's how we built the only continuously updated UCP directory on the internet.

Why does this status matter?

Universal Commerce Protocol is the standard AI shopping agents (ChatGPT, Claude, Gemini, Apple Intelligence) use to discover what a store sells, how to add items to a cart, and how to check out. If a store isn't UCP-verified, agents can still scrape it — but they'll be slower, less reliable, and far more likely to fail at checkout. UCP turns a guess into a guarantee.

Back to status

UCP Score

UCP Score for cardial.sa

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

✓Verified

A95/100

Analyzed Sep 22, 2026 · 4 recommendations ·Salla · v2026-04-08 upgrade

/ 100

UCP Conformance Score

cardial.sa publishes a conforming manifest with broad capability coverage.

Agent Discovery100

UCP Conformance88

Capability Coverage100

Working

Agent Discovery is solid (100/100).

Start Here

Use reverse-domain capability keys → Use reverse-domain payment handler keys → Use YYYY-MM-DD for handler version

Top Priorities

Use reverse-domain capability keys

A capability key does not match reverse-domain format (e.g. dev.ucp.shopping.checkout).

Medium impact Low effort

Use reverse-domain payment handler keys

A payment handler key is not in reverse-domain format.

Medium impact Low effort

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

Use reverse-domain capability keys
Use reverse-domain payment handler keys
Use YYYY-MM-DD for handler version

Consider Later(1)

Lower priority

Upgrade to the latest UCP spec version

Recommendations

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

Use reverse-domain capability keys

Medium impact Low effort ×9

A capability key does not match reverse-domain format (e.g. dev.ucp.shopping.checkout).

Why it matters

Capability namespaces use reverse-domain identifiers to avoid collisions when stores extend the spec. "checkout" is ambiguous; "dev.ucp.shopping.checkout" is unambiguous.

Show fix

"capabilities": {
  "dev.ucp.shopping.checkout": [...]
}

UCP_CAPABILITY_INVALID_KEY

Use reverse-domain payment handler keys

Medium impact Low effort

A payment handler key is not in reverse-domain format.

Why it matters

Handlers use reverse-domain identifiers (e.g. com.google.pay, com.stripe.terminal) so multiple stores can declare the same logical handler.

Show fix

"payment_handlers": {
  "com.google.pay": [...]
}

UCP_HANDLER_INVALID_KEY

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

Upgrade to the latest UCP spec version

Low impact Low effort

Your manifest declares a valid but older spec version. A newer published version is available.

Why it matters

Older versions stay valid (agents pin to the version you declare), but newer agent capabilities — embedded checkout, AP2 mandates, identity linking, 3DS payment authentication, payment terms and location lookup — only resolve against the latest spec. The manifest envelope barely moved: signing_keys went from inside ucp to the root as of 2026-04-08, and v2026-08-25 replaced it with keys (a JWK Set). Everything else in v2026-08-25 changed in the capability vocabulary, not the envelope.

Show fix

Bump version to 2026-08-25 and publish your public keys as a root-level keys array (JWK Set). Legacy signing_keys is still accepted, at the root or nested, but keys is the canonical field every verifier reads. See /specs/2026-08-25 for the full release notes.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // JWK Set, sibling of ucp, not nested inside

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

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 manifest 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 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.
Spec 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.
Validation warnings clearCore

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

No handlers declared

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.

6.8 KB4cd3604be5f5db6f

mentions UCP

# كارديــال

> كارديال متجر سعودي متخصص في الساعات الفاخرة والإكسسوارات للرجال والنساء. يقدم المتجر مجموعة واسعة من الساعات الرسمية والرياضية، بالإضافة إلى ساعات الألماس، العطور، النظارات، والإكسسوارات مثل الكبكات والأقلام والسبح. يستهدف المتجر العملاء الباحثين عن الأناقة والجودة بتصاميم فاخرة وأسعار تنافسية.
>
> تتراوح أسعار المنتجات من 162 ريال للإكسسوارات والسبح إلى أكثر من 999 ريال لساعات الألماس. يوفر المتجر خيارات تقنية حديثة تشمل الساعات الذكية ومنتجات كاردي اكس. تتوفر كافة معلومات الشروط والأحكام وسياسات الاستبدال والاسترجاع عبر الموقع لضمان تجربة تسوق موثوقة داخل المملكة العربية السعودية.
- WhatsApp: 920000244
- Mobile: 920000244
- Email: [email protected]


## Supported Languages

- العربية (rtl)

## Product Categories

- [ساعات نسائية](https://cardial.sa/ar/-/c448112447): ساعات نسائية بتصاميم فاخرة وكلاسيكية تناسب كافة المناسبات
- [ساعات رجالية](https://cardial.sa/ar/-/c1955776056): تشكيلة من الساعات الرجالية الرسمية والعملية بماركات متنوعة
- [إكسسوارات نسائية](https://cardial.sa/ar/-/c2130868541): مجموعة من الأساور والسلاسل والخواتم والحلق بتصاميم عصرية
- [إكسسوارات رجالية](https://cardial.sa/ar/-/c899591943): تشمل الأقلام الفاخرة والكبكات الرسمية والسبح والمحافظ
- [ساعات الألماس](https://cardial.sa/ar/-/c2038558527): ساعات فاخرة مرصعة بالألماس للرجال والنساء بأسعار تبدأ من 999 ريال
- [المنتجات الرقمية](https://cardial.sa/ar/-/c420584207): تشمل خاتم كاردي اكس الذكي وخاتم التسبيح وساعات الأمان للأطفال
- [العطور](https://cardial.sa/ar/-/c661317674): تشكيلة من العطور الفاخرة المختارة من كارديال
- [النظارات](https://cardial.sa/ar/-/c1596994889): نظارات شمسية وطبية بتصاميم حديثة للرجال والنساء

## Top Products

- [قلم كارديال 255073](https://cardial.sa/ar/cardial-pen-255073/p369209180): قلم فاخر بتصميم كلاسيكي للرجال، 249 ريال — ★ 4.5/5 (2 reviews)
- [قلم كارديال 245039](https://cardial.sa/ar/cardial-men-Pen-245039/p15010086): قلم رجالي رسمي للمناسبات والأعمال، 224 ريال — ★ 5/5 (3 reviews)
- [ساعة نسائية هوقو ووتش 268032](https://cardial.sa/ar/hugo-watch-women-268032/p1841178660): ساعة نسائية أنيقة من ماركة هوقو، 388 ريال — ★ 5/5 (1 reviews)
- [سبحة كارديال 265101](https://cardial.sa/ar/product-1883519282/p1883519282): سبحة رجالية فاخرة بتصميم مميز، 224 ريال — ★ 5/5 (1 reviews)
- [سلسال كريستال كارديال 265032](https://cardial.sa/ar/cardial-necklace-265032/p568743400): قلادة نسائية مرصعة بالكريستال اللامع، 312 ريال — ★ 5/5 (1 reviews)
- [ساعة نسائية كارديال 264022](https://cardial.sa/ar/cardial-women-watch-264022/p1452107765): ساعة نسائية فاخرة من ماركة كارديال، 937 ريال
- [سبحة كارديال 265267](https://cardial.sa/ar/product-800627191/p800627191): سبحة رجالية أنيقة للاستخدام اليومي، 162 ريال
- [اسوارة كارديال 265208](https://cardial.sa/ar/product-1323985033/p1323985033): سوار نسائي بتصميم عصري، 249 ريال
- [حلق كارديال 265202](https://cardial.sa/ar/product-705802749/p705802749): أقراط نسائية ناعمة للمناسبات البسيطة، 187 ريال
- [خاتم كارديال 265200](https://cardial.sa/ar/product-1464057244/p1464057244): خاتم نسائي أنيق بتصميم فريد، 187 ريال
- [ساعة رجالية هوقو ووتش 268034](https://cardial.sa/ar/hugo-watch-men-268034/p1244053134): ساعة رجالية عملية بتصميم حديث، 329 ريال
- [سلسال كريستال كارديال 255076](https://cardial.sa/ar/cardial-necklace-255076/p1310372319): سلسال نسائي مرصع بالكريستال الفاخر، 349 ريال
- [خاتم كاردي اكس](https://cardial.sa/ar/-/p1636216543): خاتم ذكي متطور يجمع بين التقنية والأناقة
- [ساعة نسائية هوقو ووتش 268057](https://cardial.sa/ar/hugo-watch-womens-watch-268057/p258480180): ساعة نسائية كاجوال للاستخدام اليومي، 329 ريال

## Buying Guides

- [المدونة](https://cardial.sa/ar/blog): مقالات تعليمية حول اختيار الساعات والعناية بالإكسسوارات
- [قصة ساعة الامبراطورة](https://cardial.sa/ar/قصة-ساعة-الامبراطورة-the-impress/page-141506147): دليل تعريفي بمميزات وتصميم ساعة الإمبراطورة الخاصة بكارديال

## Support / FAQ

- [الشروط والأحكام](https://cardial.sa/ar/الشروط-والأحكام/page-1035135058): قواعد استخدام المتجر وسياسات البيع
- [معلومات الإسترجاع والإستبدال](https://cardial.sa/ar/return-info/page-1027532867): تفاصيل سياسة إرجاع وتبديل المنتجات
- [الخصوصية](https://cardial.sa/ar/الخصوصية/page-253491020): سياسة حماية بيانات العملاء وخصوصيتهم
- [من نحن](https://cardial.sa/ar/من-نحن/page-1916449098): معلومات عن تاريخ شركة كارديال ورؤيتها في سوق الساعات

## Docs

- [API Catalog](https://cardial.sa/.well-known/api-catalog): Full list of available store API endpoints
- [MCP](https://cardial.sa/mcp): Model Context Protocol endpoint for AI tool integration
- [UCP](https://cardial.sa/.well-known/ucp): Universal Commerce Protocol discovery — agent-facing catalog search, cart, and checkout
- [Sitemap](https://cardial.sa/sitemap.xml): Complete sitemap of all store pages and products
- [Robots.txt](https://cardial.sa/robots.txt): Crawl and indexing directives for search engines
- [OAuth Discovery](https://cardial.sa/.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://cardial.sa/.well-known/ucp
HTTP Status	200
UCP Version	2026-04-08
Transports	REST, MCP
Last Observed	2026-09-22T10:11:19+00:00
Last Full Index	Sep 22, 2026 10:11 AM UTC

Embed your UCP Score

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

Live preview

Markdown

[![UCP Score for cardial.sa](https://ucpchecker.com/score/cardial.sa/badge.svg)](https://ucpchecker.com/score/cardial.sa)

HTML

<a href="https://ucpchecker.com/score/cardial.sa"><img src="https://ucpchecker.com/score/cardial.sa/badge.svg" alt="UCP Score for cardial.sa"></a>

New · Early access open

Is cardial.sa 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 cardial.sa'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.