UCP Checker
Check a store
UCP status report

deutschesee.de

deutschesee.de responded, but its profile did not pass schema validation.

Invalid
49/100
UCP Score · grade D →
4 problems · 9 passed
HTTP 200 Release "2026-08-25" Checked 21 Oct, 05:00 UTC

Findings

9 passed · 4 problems
To fix first
Problem
The profile sits behind a redirect
deutschesee.de/.well-known/ucp answers 301 redirect. The spec forbids redirects on the profile, so an agent that asks deutschesee.de stops there. Serve it directly on every host agents use. How to fix →
Problem
Declare ucp.services
ucp.services
No services declared, so agents have no transport endpoints to call. How to fix →
ucp.services
Also worth fixing
To fix
The profile has no ETag or Last-Modified header
Spec level: SHOULD. Not part of the UCP Score. How to fix →
To fix
Populate ucp.capabilities or remove it
capabilities is present but empty. How to fix →
Passed
9 OK
HTTPS, AI bot access, llms.txt, sitemap.xml, Open Graph tags, Organization schema (JSON-LD), Mobile viewport meta, Protocol version present and well-formed, Public keys published
Show all 9
  • HTTPS: Profile URL uses https://
  • AI bot access: robots.txt allows /.well-known/ucp
  • llms.txt: Found at /llms.txt
  • sitemap.xml: Found at /sitemap.xml
  • Open Graph tags: og:title and og:type/url present
  • Organization schema (JSON-LD): Organization-typed JSON-LD detected
  • Mobile viewport meta: <meta name="viewport"> present
  • Protocol version present and well-formed: Version: 2026-08-25
  • Public keys published: Keys published at the top level
Check trace

How deutschesee.de answered our check

The five ways an agent can reach this store, what each one met, and every request we made.

1 of 5 open
4 requests · 786 ms at the store · public requests only
  1. 01Hosting ↗
    Finding the profile
    Open
  2. 02Identity Linking ↗
    Acting for the buyer
    Not offered
  3. 03Embedded ↗
    In the buyer's browser
    Not offered
  4. 04Services ↗
    Calling its services
    None
  5. 05continue_url ↗
    Sending the buyer to the website
    Not declared
UCP Checkerpublic requests
  • 2 requestsFinding the profile/.well-known/ucp · 200
  • read from profileActing for the buyernot declared
  • read from profileIn the buyer's browsernot declared
  • not calledCalling its servicesnone declared
  • read from profileSending to the websitenot declared
  • 2 requestsOutside UCPhomepage · /llms.txt
Open
01 · Finding the profile2 requests
Served at /.well-known/ucp with 200 OK, 264 B. robots.txt allows /.well-known/ucp.
Not offered
02 · Acting for the buyerread from profile
The profile doesn't declare identity linking, so an agent can't act for a signed-in buyer.
Not offered
03 · In the buyer's browserread from profile
No Embedded service is declared.
None
04 · Calling its servicesnot called
No services are declared.
Not declared
05 · Sending the buyer to the websiteread from profile
No permalink declared. Whether error replies carry a continue_url shows only in an agent run.
  1. 01 PROFILEGET /.well-known/ucp → 200, 264 B of JSON786 ms
  2. 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
  3. 01 PROFILEProfile did not pass schema validation: Missing required field: ucp.serviceslocal
  4. OUTSIDE UCPGET / → 200, Organization schema found–
  5. OUTSIDE UCPGET /llms.txt → 200, 1.5 KB–
UCP profile as served 443 B · 19 lines 
{
    "ucp": {
        "version": "2026-08-25",
        "services": [],
        "capabilities": [],
        "payment_handlers": []
    },
    "keys": [
        {
            "x": "LUrh1F_jOOqx-xFeQ0FaPUT50AQlBK7hI0JdmJX1ax4",
            "y": "xyoKFAK1ncoVH4OxXy0QB5sxw5a0hib2xsMbOygy1wU",
            "alg": "ES256",
            "crv": "P-256",
            "kid": "default",
            "kty": "EC",
            "use": "sig"
        }
    ]
}
What goes in a UCP profile →Check your JSON in the Validator →Guides by store platform →
Is deutschesee.de your store?
Claim it with one DNS record.
Claim this store

Questions

Why is deutschesee.de's profile invalid?
We found a UCP profile, but it failed schema validation against the official spec. The findings on this page list what failed — usually missing required fields, wrong data types, or version mismatches. Agents reject profiles that don't validate, so this needs fixing before deutschesee.de is agent-ready.
How can deutschesee.de fix this?
Run the profile through our UCP Validator — it shows line-by-line schema deviations and how to fix each one. Most invalid profiles are quick fixes: a missing field, a typo, or an outdated spec version.
Does this mean deutschesee.de is broken for shoppers?
No — the regular website still works fine for human customers. Only AI agents that strictly validate the profile will refuse to use the UCP integration. The store just isn't agent-ready until the validation issues are resolved.
How was this UCP report for deutschesee.de generated?
Our crawler fetches deutschesee.de/.well-known/ucp directly, parses the profile against the official UCP JSON schema, checks robots.txt for its rules for AI crawlers, and runs payment-handler validation. No manual review, no opinions — just what the profile actually says. The check ran 1 day ago.
How do I get a newer result for deutschesee.de?
This page shows the stored result of our last check and when it was observed. To run a new check, use Check again on this page.
Why does this status matter?
Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.