UCP status report
chargerybh.com
chargerybh.com responded, but its profile did not pass schema validation.
HTTP 200
Release "2026-04-08"
Checked 20 Nov, 20:06 UTC
To fix first
Problem
The profile isn't served with the caching the spec requires
Served without a Cache-Control header. Spec level: MUST.
Problem
Declare a transport on the service
Service entry has no "transport" field and no legacy nested transport.
Problem
Match your release's schema
The UCP project's own validator rejects this profile against the release it declares. It rejects services, capabilities.dev.ucp.shopping.catalog, capabilities.dev.ucp.shopping.search and 2 more.
Also worth fixing
To fix
supported_versions isn't laid out the way the spec says
Spec level: SHOULD.
To fix
Move to the latest UCP protocol version
Your profile declares a valid but older protocol version. A newer one is published.
To fix
Publish a /llms.txt brand brief
No /llms.txt file detected at the root of your domain.
To fix
Your store lives on chargerybh.com; www.chargerybh.com only redirects to it
How we decided: your homepage names chargerybh.com as its canonical address; and your UCP profile is served directly at chargerybh.com/.well-known/ucp. An agent given www.chargerybh.com instead gets a redirect, and the spec tells agents not to follow one, so it stops there. Serve /.well-known/ucp directly on www.chargerybh.com too if agents may use it.
Passed
8 OK
HTTPS, AI bot access, sitemap.xml, Open Graph tags, Organization schema (JSON-LD), Mobile viewport meta, Protocol version present and well-formed, Public keys published
Show all 8
- HTTPS: Profile URL uses https://
- AI bot access: robots.txt allows /.well-known/ucp
- 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-04-08
- Public keys published: Keys published at the top level
Check trace
How chargerybh.com answered our check
What our check asked for and read, under the UCP spec's own sections, and every request we made.
- Requests
- 7
- Connections
- 5
- At the store, summed
- 2.16 s
- Network, summed
- 1.06 s
- Compressed
- 6 of 7
- Requests signed
- yes
-
Discovery↗Discovery & negotiationhow agents find the profileFound · 2 requests
-
Identity & Auth↗Identity & authenticationhow each side proves who it isSigned by us · 0 keys
-
Payment↗Payment architecturehow the store takes paymentNone declared
-
Transport↗Transport layerhow agents call the storeUnreadable
-
Capabilities↗Standard capabilitieswhat agents can do thereUnreadable
UCP CheckerUCPCheckerBot/1.0
- Signed · Web Bot Auth
- key K_DlV2MybP…
- Discovery & negotiation/.well-known/ucp · 200
GET /.well-known/ucp200 OK196 msGET www.chargerybh.com/.well-known/ucp301 Moved Permanently83 ms
- read from profileIdentity & authenticationsigned · 0 keys
- read from profilePayment architecturenone declared
- not calledTransport layerdeclared off-shape · 2026-04-08
- read from profileStandard capabilitiesdeclared off-shape · 2026-04-08
- Outside UCProbots.txt · homepage · /llms.txt
GET /robots.txt200 OK140 msGET /200 OK1,050 msGET /sitemap.xml200 OK432 msGET /llms.txt404 Not Found539 msGET /200 OK776 ms
Found
Discovery & negotiation2 requests
Served at chargerybh.com/.well-known/ucp with 200 OK, 1016 B. www.chargerybh.com only redirects to it. robots.txt allows /.well-known/ucp.
Read
Identity & authenticationread from profile
Every request we made was signed (Web Bot Auth, RFC 9421). The profile publishes no keys, so the store's own signed messages can't be checked.
None
Payment architectureread from profile
No payment handlers declared.
Unreadable
Transport layernot called
Services are declared in a shape release 2026-04-08 doesn't define: an agent that follows the spec can't find a transport or an address to call.
Unreadable
Standard capabilitiesread from profile
Capabilities are declared in a shape release 2026-04-08 doesn't define, so an agent can't tell what the store offers.
Discovery & negotiation2 requests · 200 OK · 301 Moved Permanently317 ms
GET /.well-known/ucp
200 OK
1016 B · application/json
196 ms
Answered.
- DNS 0 ms
- Wait 195 ms
- Download 0 ms
- URL
https://chargerybh.com/.well-known/ucp- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
application/json- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
application/json; charset=utf-8- Got content-encoding
gzip- Got cf-ray
a5da137d5f857c2a-EWR
GET www.chargerybh.com/.well-known/ucp
301 Moved Permanently
→ chargerybh.com/.well-known/ucp
83 ms
Redirected to https://chargerybh.com/.well-known/ucp.
- DNS 0 ms
- Connect 1 ms
- TLS 52 ms
- Wait 28 ms
- Download 0 ms
- URL
https://www.chargerybh.com/.well-known/ucp- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
application/json- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
text/html; charset=UTF-8- Got location
https://chargerybh.com/.well-known/ucp- Got cf-ray
a5da137f283180da-EWR
Outside UCP · its other files5 requests · 4 × 200 OK · 404 Not Found2,404 ms
GET /robots.txt
200 OK
21.0 KB · text/plain
140 ms
Answered.
- DNS 0 ms
- Connect 3 ms
- TLS 115 ms
- Wait 20 ms
- Download 0 ms
- URL
https://chargerybh.com/robots.txt- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
text/plain- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
text/plain; charset=utf-8- Got content-encoding
gzip- Got cache-control
public, max-age=2678400- Got cf-ray
a5da137d2ed07c2a-EWR
GET /
200 OK
542.6 KB · text/html
1,050 ms
Answered.
- DNS 0 ms
- Wait 889 ms
- Download 161 ms
- URL
https://chargerybh.com/- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
text/html- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
text/html; charset=utf-8- Got content-encoding
br- Got cf-ray
a5da137f5ec07c2a-EWR
GET /sitemap.xml
200 OK
338 B · application/xml
432 ms
Answered.
- DNS 0 ms
- Connect 104 ms
- TLS 194 ms
- Wait 132 ms
- Download 0 ms
- URL
https://chargerybh.com/sitemap.xml- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
application/xml,text/xml- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
application/xml- Got content-encoding
gzip- Got cf-ray
a5da138868644f69-EWR
GET /llms.txt
404 Not Found
539 ms
Nothing at this address.
- DNS 0 ms
- Connect 52 ms
- TLS 242 ms
- Wait 231 ms
- Download 13 ms
- URL
https://chargerybh.com/llms.txt- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept
text/plain- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
text/html; charset=utf-8- Got content-encoding
br- Got cf-ray
a5da13886cd30f41-EWR
GET /
200 OK
542.6 KB · text/html
776 ms
Answered.
- DNS 0 ms
- Connect 1 ms
- TLS 289 ms
- Wait 456 ms
- Download 28 ms
- URL
https://chargerybh.com/- Server
104.21.43.159- Sent user-agent
UCPCheckerBot/1.0 (+https://ucpchecker.com/methodology)- Sent accept-encoding
gzip, deflate, br, zstd- Sent signature-agent
sig1="https://ucpchecker.com/.well-known/http-message-signatures-directory"- Sent signature
- Web Bot Auth (RFC 9421)
- Got server
cloudflare- Got content-type
text/html; charset=utf-8- Got content-encoding
br- Got cf-ray
a5da13885c6ecb4e-EWR
- DISCOVERYProfile did not pass schema validation: Doesn't match release 2026-04-08's schema (UCP project validator): /services: is not of type "object" (and 4 more)
UCP profile as served 1016 B as served · 40 lines
{
"merchant": {
"name": "CHARGERY",
"logo_url": "https://img.zid.store/img/fit=scale-down,width=200/https://media.zid.store/ab579718-f51e-49cf-903e-f37dd67d1769/06d32932-a949-4fc7-a176-7f3206b9c12b.jpg",
"website_url": "https://chargerybh.com/?utm_source=ucp&utm_medium=ai&utm_campaign=ucp"
},
"ucp": {
"version": "2026-04-08",
"services": [
{
"spec_url": "https://ucp.dev/latest/specification/overview/",
"version": "2026-04-08",
"binding": {
"type": "rest",
"endpoint": "https://chargerybh.com/api/v1/ucp"
}
}
],
"capabilities": {
"dev.ucp.shopping.catalog": {
"version": "2026-04-08",
"spec": "https://ucp.dev/latest/specification/reference/"
},
"dev.ucp.shopping.search": {
"version": "2026-04-08",
"spec": "https://ucp.dev/latest/specification/reference/"
}
},
"payment_handlers": [],
"supported_versions": [
"2026-04-08"
]
},
"signing_keys": [],
"legal_links": {
"privacy_policy": "https://chargerybh.com/pages/privacy-policy",
"terms_of_service": "https://chargerybh.com/pages/terms-and-conditions",
"return_policy": "https://chargerybh.com/pages/refund-exchange-policy"
}
}
Is chargerybh.com your store?
Claim it with one DNS record.
Why is chargerybh.com'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. A UCP agent may not be able to use a profile that doesn't validate, so these are worth fixing first.
How can chargerybh.com fix this?
Run the profile through our UCP Validator — it shows each problem and where it is in the file. Fix those, publish the profile again, then run a new check.
Does this mean chargerybh.com is broken for shoppers?
No. This check looks only at the UCP profile, not at the website people shop on. It only affects UCP agents, which read the profile.
How was this UCP report for chargerybh.com generated?
With public requests on 20 November 2026: we asked for
chargerybh.com/.well-known/ucp and read its robots.txt, then validated the profile against the UCP release it declares and checked that its spec and schema links resolve. No sign-in, no purchase and no manual review. How we check.How do I get a newer result for chargerybh.com?
This page shows the stored result of our last check (20 November 2026). To run a new one, enter chargerybh.com on the Check 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.
