UCP status report
zuntra.com
zuntra.com responded, but its profile did not pass schema validation.
HTTP 200
Release none
Checked 20 Oct, 15:00 UTC
To fix first
Problem
Serve profile as application/json
The profile URL did not return parseable JSON. How to fix →
Also worth fixing
To fix
Publish Organization schema (JSON-LD) on the homepage
No Organization-typed JSON-LD detected on your homepage. How to fix →
To fix
Publish a /llms.txt brand brief
No /llms.txt file detected at the root of your domain. How to fix →
To fix
Publish a sitemap.xml
No sitemap.xml detected at the root of your domain. How to fix →
To fix
Add Open Graph meta tags to the homepage
OG tags missing or incomplete on your homepage. How to fix →
Passed
5 OK
HTTPS, AI bot access, Mobile viewport meta, Public keys published, No validation warnings
Show all 5
- HTTPS: Profile URL uses https://
- AI bot access: robots.txt allows /.well-known/ucp
- Mobile viewport meta: <meta name="viewport"> present
- Public keys published: Keys published at the top level
- No validation warnings: No outstanding validation issues
Check trace
How zuntra.com 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 · 292 ms at the store · public requests only
4 requests · 292 ms at the store · public requests only
-
Finding the profileOpen
-
Acting for the buyerNot offered
-
In the buyer's browserNot offered
-
Calling its servicesNone
-
Sending the buyer to the websiteNot 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, 786 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.
- 01 PROFILEGET /.well-known/ucp → 200, 786 B of JSON292 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILEProfile did not pass schema validation: Response is not a valid JSON objectlocal
- OUTSIDE UCPGET / → 200, no Organization schema found–
- OUTSIDE UCPGET /llms.txt → 200, not found–
UCP profile as served 786 B · 22 lines
<!doctype html> <html lang="en"> <head> <meta charset="UTF-8" /> <link rel="icon" type="image/x-icon" href="/favicon.ico" /> <link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png" /> <link rel="icon" type="image/png" sizes="192x192" href="/favicon-192x192.png" /> <link rel="icon" type="image/png" href="/favicon.png" /> <link rel="shortcut icon" href="/favicon.ico" /> <link rel="apple-touch-icon" href="/apple-touch-icon.png" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Zuntra</title> <script type="module" crossorigin src="/assets/index-dgYNbX2P.js"></script> <link rel="stylesheet" crossorigin href="/assets/index-DVNMRstN.css"> </head> <body class="body-sm"> <div id="root"></div> </body> </html>
Is zuntra.com your store?
Claim it with one DNS record.
Why is zuntra.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. Agents reject profiles that don't validate, so this needs fixing before zuntra.com is agent-ready.
How can zuntra.com 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 zuntra.com 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 zuntra.com generated?
Our crawler fetches
zuntra.com/.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 2 days ago.How do I get a newer result for zuntra.com?
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.
