UCP Checker
Back to status
angrybeards.cz icon
UCP Score

UCP Score for angrybeards.cz

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

✓Verified
B84/100
Analyzed Oct 14, 2026 · 3 recommendations ·Shoptet · v2026-08-25 latest
84
/ 100
UCP Score
B

Solid UCP setup on angrybeards.cz with a few gaps left to close.

Agent Discovery95
UCP Conformance91
Capability Coverage65
Biggest blockers
Repair declared transport endpoints
Working

Agent Discovery is solid (95/100).

Blocking

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

Start Here

Repair declared transport endpoints → Publish the public keys agents use to check your messages → Publish Organization schema (JSON-LD) on the homepage

Verified

angrybeards.cz publishes a valid UCP profile, with minor schema warnings.

Latency
634ms
Version
2026-08-25
Robots.txt
Allowed ✅

Top Priorities

1
Repair declared transport endpoints

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

High impact Medium effort
2
Publish the public keys agents use to check your messages

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Medium impact Medium effort
3
Publish Organization schema (JSON-LD) on the homepage

No Organization-typed JSON-LD detected on your homepage.

Medium impact Medium effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(1)

High impact, high effort

  • Repair declared transport endpoints
Incremental Gains(2)

Medium impact & effort

  • Publish the public keys agents use to check your messages
  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(0)

Lower priority

  • No items

How you compare on Shoptet

Response time benchmarked against 235 Shoptets we monitor.

fastShoptet median 686msslow
Your store
634ms
Shoptet percentile
Top 10%
Faster than 94% of Shoptet stores
Cohort range
658–755ms
p25 to p75 (middle half)

Recommendations

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

1

Repair declared transport endpoints

High impact Medium effort

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

Why it matters

A declared endpoint that does not answer stops an agent at that step, even though the profile itself validates. 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
2

Publish the public keys agents use to check your messages

Medium impact Medium effort

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Why it matters

Agents use these keys to check that checkout messages really came from you. A store that takes payment through the agent needs them. A store that sends the buyer to its own checkout page can manage without them for now.

Show fix

Create an Ed25519 key pair. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, and keep the private key on your server. Replace the key once a year, giving each new key its own "kid".

{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "<base64url-encoded-public-key>",
      "kid": "key-2026-04",
      "alg": "EdDSA"
    }
  ],
  "ucp": { ... }
}
UCP_MISSING_SIGNING_KEYS
3

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

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.

Show fix

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

Full Check Breakdown

Every signal we evaluate, grouped by category.

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

    Missing or incomplete on homepage

    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 Conformance3/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-08-25

    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.

  • No validation warningsCore

    Profile passes structural and field-level rules.

    1 warning

    Why it matters

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

  • Spec & schema URLs resolve (6)Core

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

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

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    3 of 6 capability families detected: Checkout, Cart 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

    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.angrybeards.cz/ucp/v1.

    HTTP 301

    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.

2.2 KB9288ed0154f2ea8f
# Angrybeards.cz

> Angry Beards vyrábí poctivou kosmetiku pro muže s vlastními recepturami a českou výrobou. Naše produkty jsou vyvíjeny a testovány přímo v Třebíči s důrazem na maximální funkčnost a kvalitu.

Jsme parta srdcařů, která se z garáže vypracovala mezi největší české značky pánské kosmetiky. Zakládáme si na vlastním vývoji, zpětné vazbě od našeho gangu zákazníků a otevřené komunikaci bez zbytečných příkras.

## Shopping information

* Platební metody: On-line platba kartou, Online bankovní převod, Apple Pay, Google Pay, Převodem, Dobírka, Kup teď, zacáluj později, Twistuj na třetiny.
* Doprava: Zásilkovna, GLS, Balíkovna, osobní odběr v Třebíči a na prodejnách Melody.

- [FAQ](https://www.angrybeards.cz/faq/): Odpovědi na nejčastější dotazy od objednávek až po používání produktů.
- [Kontakt](https://www.angrybeards.cz/kontakty/): Zákaznická podpora dostupná v pracovní dny od 8:00 do 16:00.
- [Garance spokojenosti](https://www.angrybeards.cz/garance-spokojenosti/): Možnost vrácení peněz, pokud vám produkt nesedne.
- [Obchodní podmínky](https://www.angrybeards.cz/obchodni-podminky/): Kompletní právní informace a podmínky nákupu.

## Categories

- [Vousy](https://www.angrybeards.cz/vousy/): Kompletní péče o vousy od olejů po balzámy.
- [Kule](https://www.angrybeards.cz/kule/): Specializovaná intimní hygiena pro muže.
- [Vlasy](https://www.angrybeards.cz/vlasy/): Stylingové přípravky a péče o vlasy.
- [Tělo](https://www.angrybeards.cz/telo/): Sprchové gely, deodoranty a další tělová kosmetika.
- [Vůně](https://www.angrybeards.cz/vune/): Pánské parfémy a vůně s osobitým charakterem.
- [Sady](https://www.angrybeards.cz/sady/): Výhodné balíčky produktů vhodné jako dárek.
- [Spoďáry](https://www.angrybeards.cz/calm-b-spodni-pradlo/): Pohodlné pánské spodní prádlo.

## Content

- [Sport vs. pocení](https://www.angrybeards.cz/sport-vs-poceni/): Průvodce jak zůstat fresh při sportovních aktivitách.
- [Připrav tělo na zimu](https://www.angrybeards.cz/priprav-telo-na-zimu/): Tipy pro péči o pokožku v chladném období.

## Optional

- [Sitemap](https://www.angrybeards.cz/sitemap.xml)
View source ↗

Capabilities Detected

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

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://angrybeards.cz/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports REST
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 angrybeards.cz badge for https://ucpchecker.com/score/angrybeards.czLive preview
Markdown
[![UCP Score for angrybeards.cz](https://ucpchecker.com/score/angrybeards.cz/badge.svg)](https://ucpchecker.com/score/angrybeards.cz)
HTML
<a href="https://ucpchecker.com/score/angrybeards.cz"><img src="https://ucpchecker.com/score/angrybeards.cz/badge.svg" alt="UCP Score for angrybeards.cz"></a>
New · Early access open
Is angrybeards.cz 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 angrybeards.cz'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.