UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
bonsai.de is conforming and ready for agent discovery and checkout.
Agent Discovery is solid (100/100).
Repair declared transport endpoints — One or more declared transport endpoints did not respond when probed.
Repair declared transport endpoints → Fix broken spec or schema URLs → Confirm checkout-link redirect strategy
One or more declared transport endpoints did not respond when probed.
One or more spec/schema URLs declared in the manifest do not resolve.
payment_handlers is present but empty.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
All improvements ranked by priority, with evidence and actionable fixes.
One or more declared transport endpoints did not respond when probed.
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.
One or more spec/schema URLs declared in the manifest 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 manifest setup. See the Full Check Breakdown for the specific URLs that failed.
payment_handlers is present but empty.
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.
Your manifest declares a valid but older spec version. A newer published version is available.
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.
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 insideEvery signal we evaluate, grouped by category.
Can AI agents find your store and its UCP manifest?
Manifest served over a secure connection.
Manifest URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Manifest 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 manifest.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published manifest 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.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your manifest 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 manifest meet the published spec?
Manifest structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject manifests with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-04-08
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.
Manifest passes structural and field-level rules.
1 warning
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 13 spec/schema URLs declared across the manifest to confirm agents can fetch each one.
Did not resolve: https://ucp.dev/2026-04-08/schemas/shopping/catalog.json
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 capabilities detected
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, EMBEDDED, A2A
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.
Empty array — checkout-link redirect strategy
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://www.bonsai.de/ucp/v1.
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 manifest itself looks perfect.
Live reachability check against https://www.bonsai.de/ucp/embedded.
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 manifest itself looks perfect.
Live reachability check against https://www.bonsai.de/ucp/a2a.
Host responded with HTTP 405 — 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 manifest itself looks perfect.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# Bonsai.de
> This is a Shopware-powered online shop. This file provides AI assistants with a concise entry point to public sales channel information.
> Only public shop information is described here; account, order, payment, and checkout actions require explicit user interaction and normal authentication.
## Public resources
- [Home](/): Start page for this storefront.
- [Search](/search): Search the public product catalogue.
- [Sitemap](/sitemap.xml): Public sitemap for discoverable pages.
- [Imprint](/page/cms/9214c773e1c248bd8e8841c9d3e15d28)
- [Privacy policy](/page/cms/905e4ad76c6f402c981b46c83fc29fae)
- [Terms](/page/cms/7012410d349f441a9798f1f0a5d80e73)
- [Shipping/payment information](/page/cms/ff638c19bc7b417cb25819a9a329a832)
- [Revocation/cancellation policy](/page/cms/edc40c04ea6047379cc89d0dc7bdb0f6)
- [Robots policy](/robots.txt): Crawling and access rules.
- [Agent instructions](/AGENTS.md): Guidance for AI agents interacting with this shop.
## Localization
- Current language: Deutsch (de-DE)
- Current currency: EUR (Euro)
- Supported languages: es-ES (Spanisch, Spanien), de-DE (Deutsch, Deutschland), en-GB (Englisch, Vereinigtes Königreich), fr-FR (Französisch, Frankreich), it-IT (Italienisch, Italien), nl-NL (Niederländisch, Niederlande)
- Supported currencies: EUR (Euro)
## Guidance
- Use public sales channel resources as the source of truth.
- Verify product prices, availability, delivery information, taxes, and legal information on the live sales channel before presenting them as current.
- Prefer canonical storefront URLs or documented Store API routes when linking to products, categories, content pages, or policies.
- Respect `robots.txt`, rate limits, and normal checkout boundaries.
## Agentic commerce
- [UCP profile](/.well-known/ucp): Machine-readable Universal Commerce Protocol profile for this sales channel.
Use the UCP profile as the source of truth for enabled agentic commerce capabilities, supported transports, endpoint URLs, signing keys, and protocol versions. Only use capabilities and transports advertised in the profile.| Cart ✓ Bound | 2026-04-08 |
| Discount Extension ✓ Bound | 2026-04-08 |
| Order Management ✓ Bound | 2026-04-08 |
| Catalog ✓ Bound | 2026-04-08 |
| Checkout ✓ Bound | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://bonsai.de/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | REST, EMBEDDED, A2A |
| 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/bonsai.de)<a href="https://ucpchecker.com/score/bonsai.de"><img src="https://ucpchecker.com/score/bonsai.de/badge.svg" alt="UCP Score for bonsai.de"></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 bonsai.de'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.