ecenticecentic
How it worksResourcesPricingBlog
Install now
ASCII-art illustration of a shield

Free to use · No account required · Live /.well-known/ucp fetch

UCP Validator

Check whether a storefront publishes a valid Universal Commerce Protocol profile at /.well-known/ucp and whether shopping agents can read it without friction.

Validate a domainOpen playground
01

What the validator inspects.

A live fetch of your public profile, parsed against the UCP spec, with agent access surfaced from robots.txt.

Universal Commerce Protocol

Universal Commerce Protocol

/.well-known/ucp

"capabilities":

- dev.ucp.shopping.catalog.search

- dev.ucp.shopping.catalog.lookup

- dev.ucp.shopping.cart

- dev.ucp.shopping.checkout

- dev.ucp.shopping.fulfillment

- dev.ucp.shopping.discount

- dev.ucp.shopping.order

Endpoint reachability

We request the public HTTPS domain and confirm that /.well-known/ucp responds.

Schema hygiene

The response body is parsed as JSON and checked for UCP spec errors and warnings.

Agent access

robots.txt is reviewed so you can see whether major shopping and indexing bots are blocked.

02

Run a live validation.

Paste a domain and we fetch the live profile, parse every service and capability, then report spec errors and agent access.

Universal Commerce Protocol logo

Live fetch

HTTPS · spec 2026-08-25

GET /.well-known/ucp HTTP/1.1
Host: yourdomain.com
Accept: application/json
UCP-Agent: profile="https://ucp.dev/..."

We request the public profile, parse services and capabilities, then surface spec issues and agent access from robots.txt.

Check a domain

Root domain only — acme.com or www.acme.com. We always validate the HTTPS version.

GET /.well-known/ucp HTTP/1.1
Host: store.example.com
Accept: application/json
UCP-Agent: profile="https://ucp.dev/..."

HTTP/1.1 200 OK
Content-Type: application/json

{
  "ucp": {
    "version": "2026-08-25",
    "services": {
      "dev.ucp.shopping": [ ... ]
    },
    "capabilities": {
      "dev.ucp.shopping.cart": [ ... ],
      "dev.ucp.shopping.checkout": [ ... ]
    },
    "payment_handlers": { ... }
  },
  "keys": [ { "kty": "EC", ... } ]
}

What we validate

HTTPS & reachability

Profile discovery

/.well-known/ucp

Services & transports

REST · MCP · A2A

Capabilities

dev.ucp.shopping.*

Payment handlers

payment.handlers[]

Signing keys

keys[] · RFC 9421

Supported versions

supported_versions[]

Agent access

robots.txt

03

Questions before you validate.

What the checker covers, where profiles live, and how agent access is surfaced.

It requests the public HTTPS domain, confirms /.well-known/ucp responds, parses the body as JSON, and reports UCP spec errors and warnings so you know the profile is well formed.

At /.well-known/ucp on your storefront's public HTTPS domain. The validator fetches that exact path and shows whether it is reachable.

Yes. The validator reviews robots.txt so you can see whether major shopping and indexing bots are allowed to reach your Universal Commerce Protocol profile without friction.

All free toolsValidate a domain

Free · No account required · Live fetch

Free store check

Find out which products AI agents skip.

Install free on Shopify or WooCommerce and see your AI score in minutes.

Install on ShopifyInstall on WooCommerce
ecentic

Get the sale when AI does the shopping.

Built for the agent economy
Product
  • Features
  • How it works
  • Pricing
  • Product Listings
Platforms
  • Shopify
  • WooCommerce
  • Enterprise
Resources
  • Developer docs
  • API reference
  • Resources
  • Blog
  • Compare
  • UCP Validator
  • WebMCP scanner
  • UCP Playground
  • Book a demo
Company
  • About
  • Support
  • AI instructions
  • Privacy policy
  • Terms of service

© 2026 ecentic. All rights reserved.

Made for merchants who'd rather sell to robots than lose to them.

ECENTIC ShPK · NIPT M61628008M · Pallatet Merkaj, Hyrja 1, Dera 12, Rruga Muhamed Deliu, Qesarakë, 1030 Tiranë, Albania · +355 68 459 4667 · support@ecentic.ai