UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
flowers.ucpsandbox.com publishes a conforming profile with broad capability coverage.
UCP Conformance is solid (98/100).
Fix broken spec or schema URLs → Publish Organization schema (JSON-LD) on the homepage
One or more spec/schema URLs declared in the profile do not resolve.
No Organization-typed JSON-LD detected on your homepage.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 122 Customs we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more spec/schema URLs declared in the profile do not resolve.
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 profile setup. See the Full Check Breakdown for the specific URLs that failed.
No Organization-typed JSON-LD detected on your homepage.
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 profile data to a recognizable entity.
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>Every signal we evaluate, grouped by category.
Can AI agents find your store and its UCP profile?
Profile served over a secure connection.
Profile URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Profile fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the profile.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
Found at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Missing or incomplete on homepage
Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your profile meet the published spec?
Profile structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-08-25
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.
signing_keys present
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Profile passes structural and field-level rules.
No outstanding validation issues
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 26 spec/schema URLs declared across the profile to confirm agents can fetch each one.
Did not resolve (3 of 26): https://ucp.dev/2026-08-25/specification/location/search, https://ucp.dev/2026-08-25/specification/location/lookup, https://mock.dev/ucp/payment-handler
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.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
4 of 6 capability families detected: Checkout, Cart Management, Order Management, Catalog. A family counts once however many namespaces or extensions declare it.
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
REST, MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
1 handler registered
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://flowers.ucpsandbox.com/ucp.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
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.
Live reachability check against https://flowers.ucpsandbox.com/mcp.
tools/list returned a JSON-RPC response in 253ms
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.
Live reachability check against https://flowers.ucpsandbox.com/ucp/common.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
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.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# Northlight Flowers
> Hand-tied bouquets, plants and arrangements. A reference store for shopping agents.
> Reference test stores. Nothing here is for sale: test cards only, no goods ship.
Reference store operated by UCP Sandbox. UCP version 2026-08-25.
Everything an agent can do here is also possible for a person on the same pages: same products, same carts, same orders.
## Machine surfaces
- UCP profile: https://flowers.ucpsandbox.com/.well-known/ucp
- UCP REST binding: https://flowers.ucpsandbox.com/ucp/ (OpenAPI at https://flowers.ucpsandbox.com/ucp/openapi.json)
- MCP endpoint (JSON-RPC): https://flowers.ucpsandbox.com/mcp
- WebMCP: storefront pages register tools on document.modelContext
## Catalogue
- [Bouquets](https://flowers.ucpsandbox.com/collections/bouquets): Hand-tied that morning, in three sizes. (24 products)
- [Arrangements](https://flowers.ucpsandbox.com/collections/arrangements): Delivered ready, in a vase, box or basket. (18 products)
- [Plants](https://flowers.ucpsandbox.com/collections/plants): Indoor and outdoor, potted and thriving. (23 products)
- [Dried & Preserved](https://flowers.ucpsandbox.com/collections/dried-preserved): Lasts for months without water. (10 products)
- [Occasions](https://flowers.ucpsandbox.com/collections/occasions): Birthdays, new babies, sympathy and seasons. (14 products)
- [Vases & Pots](https://flowers.ucpsandbox.com/collections/vases-pots): Something to put them in. (9 products)
- [Accessories](https://flowers.ucpsandbox.com/collections/accessories): Tools, wrap, cards and add-ons. (12 products)
## Policies
- Returns: Fresh flowers and plants can be returned within 14 days if they arrive damaged or wilted: tell us within 48 hours of delivery with a photo and we refund or resend. Vases, tools and dried flowers can be returned unused within 30 days for a full refund. Sale items can be returned for store credit.
- Delivery: Standard delivery takes 3 to 5 working days. Express US delivery is 1 to 2 days, international express 2 to 4 days. Nothing ships from this store: it is a test store and every order is simulated.
- Cancellation: Orders can be cancelled free of charge until they are marked shipped.
- Freshness promise: Cut flowers are guaranteed to last seven days from delivery with fresh water and flower food.
## Testing
- Payment instruments: instr_1 (Visa …1234, succeeds); instr_2 (Mastercard …5678, succeeds); instr_fail (Visa …0000, declines)
- Discount codes: 10OFF, WELCOME20, FIXED500
- Fulfillment: shipping (std-ship, exp-ship-us, exp-ship-intl); pickup (pickup-first, pickup-next-day)
## FAQ
- Q: Can I return sale items? A: Yes, within 14 days for store credit.
- Q: Do you deliver on Sundays? A: No. Standard and express deliveries run Monday to Saturday.
- Q: Are the flowers real? A: The catalogue is real; the shop is not. This is a reference store for testing agents. Test cards only, nothing ships.
- Q: Which payment methods do you accept? A: Test instruments only: Visa ending 1234 and Mastercard ending 5678 succeed; Visa ending 0000 is declined.| Cart ✓ Bound | 2026-08-25 |
| Discount Extension ✓ Bound | 2026-08-25 |
| Buyer Consent Extension ✓ Bound | 2026-08-25 |
| Order Management ✓ Bound | 2026-08-25 |
| Checkout ✓ Bound | 2026-08-25 |
| Fulfillment Extension ✓ Bound | 2026-08-25 |
| Location Lookup ✓ Bound | 2026-08-25 |
| Location Search ✓ Bound | 2026-08-25 |
| Catalog Lookup ✓ Bound | 2026-08-25 |
| Catalog Search ✓ Bound | 2026-08-25 |
| UCP Status | Verified |
| Endpoint | https://flowers.ucpsandbox.com/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-08-25 |
| Transports | REST, MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/flowers.ucpsandbox.com)<a href="https://ucpchecker.com/score/flowers.ucpsandbox.com"><img src="https://ucpchecker.com/score/flowers.ucpsandbox.com/badge.svg" alt="UCP Score for flowers.ucpsandbox.com"></a>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.
Track flowers.ucpsandbox.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.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.