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

It means alghomlas.sa publishes a valid UCP profile at /.well-known/ucp, the profile 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 alghomlas.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 alghomlas.sa use for UCP?

Our detection identifies alghomlas.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 profile declares.

How was this UCP report for alghomlas.sa generated?

Our crawler fetches alghomlas.sa/.well-known/ucp directly, parses the profile 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 profile actually says. The check ran 18 hours ago.

How often is alghomlas.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 alghomlas.sa

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

✓Verified

A95/100

Analyzed Oct 8, 2026 · 4 recommendations ·Salla · v2026-04-08 upgrade

/ 100

UCP Score

alghomlas.sa publishes a conforming profile with broad capability coverage.

Agent Discovery100

UCP Conformance90

Capability Coverage95

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

Top Priorities

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

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

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 111 Sallas we monitor.

fastSalla median 529msslow

Your store

580ms

Salla percentile

Below median

Faster than 39% of Salla stores

Cohort range

406–636ms

p25 to p75 (middle half)

Recommendations

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

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

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

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

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.

Functional probes ran Oct 5, 2026.

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 Conformance4/5 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.
Spec/schema URL resolvesCore

Resolves the declared spec/schema URL to confirm agents can fetch it.

All 1 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 Coverage4/6 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.
REST transport reachableInterop

Live reachability check against https://alghomlas.sa/_app/ucp.

Host responded with HTTP 410 — endpoint reachable but path may be method-restricted

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 profile itself looks perfect.
MCP transport reachableInterop

Live reachability check against https://alghomlas.sa/_app/ucp/mcp.

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

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 profile itself looks perfect.

/llms.txt content

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

145 Bddf3dd6f3856ad84

mentions UCP

## Docs

- [UCP](https://alghomlas.sa/.well-known/ucp): Universal Commerce Protocol discovery — agent-facing catalog search, cart, and checkout

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://alghomlas.sa/.well-known/ucp
HTTP Status	200
UCP Version	2026-04-08
Transports	REST, MCP
Last Observed	2026-10-08T16:58:05+00:00
Last Full Index	Oct 8, 2026 4:58 PM 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 alghomlas.sa](https://ucpchecker.com/score/alghomlas.sa/badge.svg)](https://ucpchecker.com/score/alghomlas.sa)

HTML

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

New · Early access open

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