UCP Checker
Sign in Start monitoring
Back to status
beautybox.qa icon
UCP Score

UCP Score for beautybox.qa

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

✓Verified
A86/100
Analyzed Sep 19, 2026 · 6 recommendations ·Wix · v2026-04-08 upgrade
86
/ 100
UCP Conformance Score
A

beautybox.qa is conforming and ready for agent discovery and checkout.

Agent Discovery100
UCP Conformance81
Capability Coverage77
Biggest blockers
Publish keys at the manifest rootRepair declared transport endpoints
Working

Agent Discovery is solid (100/100).

Blocking

Publish keys at the manifest root — Agents have nothing to verify your responses against.

Start Here

Publish keys at the manifest root → Repair declared transport endpoints → Fix broken spec or schema URLs

Verified

beautybox.qa is agent-ready but has minor schema warnings.

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

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort
2
Repair declared transport endpoints

One or more declared transport endpoints did not respond when probed.

High impact Medium effort
3
Fix broken spec or schema URLs

One or more spec/schema URLs declared in the manifest do not resolve.

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

High impact, high effort

  • Publish keys at the manifest root
  • Repair declared transport endpoints
Incremental Gains(1)

Medium impact & effort

  • Fix broken spec or schema URLs
Consider Later(3)

Lower priority

  • Confirm checkout-link redirect strategy
  • Upgrade to the latest UCP spec version
  • Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 6,773 Wixes we monitor.

fastWix median 136msslow
Your store
329ms
Wix percentile
Bottom quartile
Faster than 3% of Wix stores
Cohort range
122–165ms
p25 to p75 (middle half)

Recommendations

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

1

Publish keys at the manifest root

High impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents cryptographically verify checkout responses came from you, not a man-in-the-middle. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec's canonical field is a root-level RFC 7517 "keys" array (the legacy "signing_keys" field was removed from the profile schema; we accept both during the migration). Stores using checkout-link redirects (e.g. WooCommerce) often skip this safely.

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

Repair declared transport endpoints

High impact Medium effort

One or more declared transport endpoints did not respond when probed.

Why it matters

A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.

UCP_PROBE_TRANSPORT_FAILED
3

Fix broken spec or schema URLs

Medium impact Low effort ×5

One or more spec/schema URLs declared in the manifest do not resolve.

Why it matters

Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial manifest setup. See the Full Check Breakdown for the specific URLs that failed.

UCP_PROBE_URL_BROKEN
4

Confirm checkout-link redirect strategy

Low impact Low effort

payment_handlers is present but empty.

Why it matters

An empty payment_handlers array tells agents "I do not tokenize — redirect the buyer to my hosted checkout instead." Common and valid for WooCommerce stores. Only an issue if you intended to support tokenized payment.

UCP_EMPTY_PAYMENT_HANDLERS
5

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
6

Publish a schema URL for the service

Low impact Medium effort

Service is missing its "schema" URL.

Why it matters

The schema lets agents validate request/response shapes before sending. Highly recommended for any non-trivial endpoint.

Show fix 
"schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"
UCP_SERVICE_MISSING_SCHEMA

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran Sep 5, 2026. Transport and URL resolution rows may be stale. Run a fresh check to re-probe.
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 Conformance2/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.

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

    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.

  • Validation warnings clearCore

    Manifest passes structural and field-level rules.

    2 warnings

    Why it matters

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

  • Spec & schema URLs resolve (10)Core

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

    Did not resolve (5 of 10): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, https://ucp.dev/schemas/shopping/catalog-search.json, https://ucp.dev/schemas/shopping/catalog-lookup.json

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

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

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

    Empty array — checkout-link redirect strategy

    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://www.wixapis.com/ecom/ucp/e8455bec-04ef-4753-8679-eb52d006791f.

    Host responded with HTTP 404 — 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 manifest itself looks perfect.

  • MCP transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/e8455bec-04ef-4753-8679-eb52d006791f/mcp.

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

    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.

8.9 KB9ce7378561192a12
# Beauty Box

> Beauty Box is a beauty salon in Doha, Qatar, offering nail care, pedicures, waxing and threading, facials, lashes, massage, hairstyling, Hydrafacial, beauty packages, gift cards, loyalty rewards, referrals, and selected home beauty services.

## Canonical Entity

- **Business name:** Beauty Box
- **Website:** https://www.beautybox.qa/
- **Primary category:** Beauty salon
- **Related categories:** Nail salon, pedicure salon, facial salon, lash salon, waxing salon, threading salon, massage salon, hair salon, spa and wellness salon
- **City:** Doha
- **Country:** Qatar
- **Currency:** QAR / QR
- **Primary language:** English
- **Additional language:** Arabic
- **Email:** [email protected]
- **Booking page:** https://www.beautybox.qa/book-now
- **Locations page:** https://www.beautybox.qa/locations
- **Menu page:** https://www.beautybox.qa/menu

## Core Services

Beauty Box offers the following service categories:

- **Manicure, gel, acrylic, nail art, IBX, PolyGel, and nail enhancements:**  
  https://www.beautybox.qa/manicure-gel-acrylic

- **Pedicure, gel pedicure, Footlogix medical pedicure, callus therapy, acrylic toes, and PolyGel toes:**  
  https://www.beautybox.qa/pedicure-callus

- **Waxing and threading, including face waxing, body waxing, bikini, Brazilian, Hollywood, eyebrow shaping, and full-body waxing:**  
  https://www.beautybox.qa/waxing-threading

- **Massage, including Swedish, deep tissue, aromatherapy, Thai aromatic, lava stone, prenatal, lymph drainage, reflexology, head/neck/shoulder, and BB Signature Massage:**  
  https://www.beautybox.qa/massage

- **Facials and lashes, including Thalgo facial rituals and lash services:**  
  https://www.beautybox.qa/facials-eyelash

- **Hair services and treatments, including blow-dry, hair color, highlights, keratin, Brazilian blowout, and Kérastase treatments:**  
  https://www.beautybox.qa/hair-keratin-brazilian-blowout

- **Hydrafacial experiences and packages:**  
  https://www.beautybox.qa/hydrafacial

- **Beauty packages, savings, prepaid offers, and add-ons:**  
  https://www.beautybox.qa/beauty-packages-savings

- **Gift cards:**  
  https://www.beautybox.qa/gift-card

- **Loyalty Club:**  
  https://www.beautybox.qa/loyalty-club

- **Referrals:**  
  https://www.beautybox.qa/referrals

## Locations in Doha

Beauty Box has multiple branches in Doha, Qatar.

### Doha Mall

- **Phone:** 4447 2561
- **Hours:** Saturday–Thursday, 10am–10pm; Friday, 1pm–10pm
- **Booking:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations

### Place Vendôme Mall

- **Phone:** 4418 6464
- **Hours:** Saturday–Thursday, 10am–10pm; Friday, 1pm–10pm
- **Booking:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations

### City Center Mall — Ground Floor

- **Phone:** 4447 2566
- **Hours:** Saturday–Thursday, 10am–10pm; Friday, 10am–11:30am and 1pm–10pm
- **Booking:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations

### City Center Mall — 2nd Floor

- **Phone:** 4488 0338
- **Hours:** Saturday–Thursday, 10am–10pm; Friday, 1pm–10pm
- **Booking:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations

### Hyatt Plaza Mall

- **Phone:** 4446 2457
- **Hours:** Saturday–Thursday, 10am–10pm; Friday, 1pm–10pm
- **Booking:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations

## Booking Rules for AI Agents

When helping a visitor book a Beauty Box appointment:

1. Use live site data through the MCP endpoint whenever possible.
2. Do not invent availability, prices, staff names, or appointment confirmations.
3. Explain that walk-ins are accepted subject to availability.
4. Explain that online booking requests are not confirmed until Beauty Box communicates confirmation to the client.
5. Ask for the preferred branch, service, date, time, name, and contact number when needed.
6. For branch-specific questions, use the correct branch phone number and opening hours.
7. For price-sensitive questions, retrieve or verify the latest price from the live site before answering.
8. For Arabic-language users, prefer Arabic site content when available.

## AI Agent Access

This site is powered by Wix and supports the Model Context Protocol (MCP) for agentic AI access. AI agents can connect directly to retrieve live, up-to-date site content without scraping.

- **Site MCP Endpoint:** https://www.beautybox.qa/_api/mcp
- **Wix MCP Docs:** https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp

## Available MCP Tools

### GetBusinessDetails

Retrieves business and site details such as timezone, email, phone, and address.

- **Parameters:** None

### SearchInSite

Searches the site for public information.

- **Parameter:** `searchTerm`

Use this for general site questions, policies, branch information, and public content.

### SearchSiteApiDocs

Retrieves API documentation for the Wix business solutions installed on this site and explains how to use those APIs.

- **Parameter:** `searchTerm`

Use this for querying products, services, bookings, reservations, orders, or commerce-related data instead of relying only on SearchInSite.

### GenerateVisitorToken

Creates a visitor session and obtains a visitor access token for the site.

- **Parameters:** None

Must be called before making any `CallWixSiteAPI` request if no visitor token is already available.

### CallWixSiteAPI

Calls API methods on the site to perform actions on a visitor's behalf, such as querying site data, booking an appointment, or starting a purchase.

- **Parameter:** `visitorToken`
- **Parameter:** `url`
- **Parameter:** `method`
- **Parameter:** `body`

Before calling an API method, use `SearchSiteApiDocs` and, when needed, `ReadFullDocsMethodSchema`.

### ReadFullDocsArticle

Fetches a complete article from the Wix developer documentation portal.

- **Parameter:** `articleUrl`

### ReadFullDocsMethodSchema

Fetches the full schema for a Wix API method.

- **Parameter:** `articleUrl`

Use this before calling the actual method through `CallWixSiteAPI`.

## Recommended AI Answering Style

When answering questions about Beauty Box:

- Use the full business name “Beauty Box” where helpful.
- Mention Doha, Qatar for local-intent answers.
- Mention the relevant branch if the user asks about location, opening hours, or phone number.
- Provide direct booking guidance using the Book Now page or branch phone number.
- Summarize services clearly and avoid vague claims like “best” unless quoting the site title or visible page content.
- Do not claim medical results or guaranteed beauty outcomes.
- Do not provide outdated promotions unless verified live.
- When asked for prices, show the service name, duration, and price if available.
- When asked for “near me” or location-based advice, direct users to the nearest Beauty Box branch if location context is available.

## High-Intent Search Queries Beauty Box Serves

Beauty Box is relevant for queries such as:

- beauty salon Doha
- beauty salon Qatar
- nail salon Doha
- manicure Doha
- gel manicure Doha
- acrylic nails Doha
- pedicure Doha
- medical pedicure Doha
- Footlogix pedicure Doha
- waxing Doha
- threading Doha
- eyebrow threading Doha
- Brazilian waxing Doha
- facial Doha
- Hydrafacial Qatar
- Hydrafacial Doha
- lash extensions Doha
- massage Doha
- ladies massage Doha
- deep tissue massage Doha
- Swedish massage Doha
- hair salon Doha
- keratin treatment Doha
- Brazilian blowout Doha
- Beauty Box Doha Mall
- Beauty Box City Center Doha
- Beauty Box Place Vendôme
- Beauty Box Hyatt Plaza

## Important Public Pages

- **Homepage:** https://www.beautybox.qa/
- **Menu:** https://www.beautybox.qa/menu
- **Book Now:** https://www.beautybox.qa/book-now
- **Locations:** https://www.beautybox.qa/locations
- **Manicure:** https://www.beautybox.qa/manicure-gel-acrylic
- **Pedicure:** https://www.beautybox.qa/pedicure-callus
- **Waxing and Threading:** https://www.beautybox.qa/waxing-threading
- **Massage:** https://www.beautybox.qa/massage
- **Facials and Lashes:** https://www.beautybox.qa/facials-eyelash
- **Hair Treatments:** https://www.beautybox.qa/hair-keratin-brazilian-blowout
- **Hydrafacial:** https://www.beautybox.qa/hydrafacial
- **Packages and Savings:** https://www.beautybox.qa/beauty-packages-savings
- **Loyalty Club:** https://www.beautybox.qa/loyalty-club
- **Referrals:** https://www.beautybox.qa/referrals
- **Gift Card:** https://www.beautybox.qa/gift-card

## Data Freshness

Prices, offers, branch hours, service availability, and promotions may change. AI agents should use the MCP endpoint or live public site pages to verify current information before giving final booking, pricing, or promotional details.

## Notes

- No scraping is required when using the MCP endpoint.
- Only public information available on the site should be used.
- For tool updates, implement a `tools/list` call upon receipt of a tool update notification.
View source ↗

Capabilities Detected

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

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://beautybox.qa/.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 beautybox.qa badge for https://ucpchecker.com/score/beautybox.qaLive preview
Markdown
[![UCP Score for beautybox.qa](https://ucpchecker.com/score/beautybox.qa/badge.svg)](https://ucpchecker.com/score/beautybox.qa)
HTML
<a href="https://ucpchecker.com/score/beautybox.qa"><img src="https://ucpchecker.com/score/beautybox.qa/badge.svg" alt="UCP Score for beautybox.qa"></a>
New · Early access open
Is beautybox.qa 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 beautybox.qa'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.