Can AI agents find your store and its UCP manifest?

• HTTPSCore

  Manifest served over a secure connection.

  Manifest 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 manifest reachableCore

  Manifest 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 manifest.

  robots.txt allows /.well-known/ucp

  Why it matters

  Agents respect robots.txt. Even a published manifest 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.

  Missing or incomplete on homepage

  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.

  Organization-typed JSON-LD detected

  Why it matters

  Gives agents a structured representation of your brand identity — used to verify you are who your manifest 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.

Does your manifest meet the published spec?

• Manifest passes schema validationCore

  Manifest structure conforms to the published UCP spec.

  No structural errors

  Why it matters

  Strict UCP agents reject manifests 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.

  signing_keys present

  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

  Manifest 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 (11)Core

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

  All 11 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.

What operations can agents actually perform?

• Capabilities declaredCore

  Number of agent-readable capabilities under ucp.capabilities.

  3 capabilities detected

  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, MCP

  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.serverkast.com/agent/ucp.

  Host responded with HTTP 404 — endpoint reachable but path may be method-restricted

  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 manifest itself looks perfect.

• MCP transport reachableInterop

  Live reachability check against https://www.serverkast.com/agent/mcp.

  tools/list returned a JSON-RPC response in 384ms

  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 manifest itself looks perfect.