/.well-known/ucp manifest is a machine-readable contract between your store and AI agents. It communicates three things: what commerce capabilities you support, where agents should call to use each one, and how those calls should be structured. Think of it as a robots.txt for agentic commerce — a declaration of what’s available and how to interact with it. This page documents every field you can include.
Full schema reference
/.well-known/ucp
Top-level fields
The UCP spec version this manifest targets. Currently
"1.0". Agents use this to determine which features and schemas to expect.ISO 8601 timestamp of when the manifest was last modified (e.g.
"2026-04-10T00:00:00Z"). Helps agents and caching layers determine freshness.Optional merchant identity block. Provides context for agents and platforms indexing your store.
Your store’s display name.
Canonical URL for your store homepage.
Absolute URL to your store logo. Use a square PNG or SVG for best results.
Map of capability name to configuration object. Must include at least
product_catalog and checkout.product_catalog capability
Absolute HTTPS URL for your catalog endpoint. Agents send
GET requests here to fetch products.Response format. Accepted values:
"json", "xml". Defaults to "json" if omitted.Capability version. Increment this when you change the request or response shape in a breaking way.
Set to
true if your catalog endpoint accepts a ?q= query parameter for keyword search. If false or omitted, agents will not attempt search queries.List of filter query parameters your endpoint accepts. Common values:
"category", "price_range", "availability", "brand".Set to
true if your catalog endpoint supports page-based or cursor-based pagination via a next URL in the response.checkout capability
Absolute HTTPS URL for your checkout endpoint. Agents
POST cart and shipping data here.HTTP methods your checkout endpoint accepts. Typically
["POST"].Set to
true if agents must send authentication credentials with checkout requests. Most implementations set this to false and handle authentication via payment tokens.Capability version. Increment this if you change the checkout request or response schema in a breaking way.
Payment method types your checkout endpoint accepts. Common values:
"card", "paypal", "upi", "apple_pay", "google_pay".Optional capabilities
shipping
Declare a shipping capability if you want agents to request real-time shipping quotes before presenting checkout options to the customer.
Absolute HTTPS URL for your shipping rates endpoint.
HTTP methods accepted. Typically
["POST"].orders
Declare an orders capability to allow agents to look up order status and tracking on the customer’s behalf.
Absolute HTTPS URL for your order management endpoint.
HTTP methods accepted. Typically
["GET", "POST"].returns
Declare a returns capability to allow agents to initiate return requests without the customer visiting your site.
Absolute HTTPS URL for your returns endpoint.
HTTP methods accepted. Typically
["POST"].Versioning
Update theupdated_at timestamp whenever you modify the manifest. Increment a capability’s version field when the request or response shape for that capability changes in a breaking way.
Agents may cache your manifest for up to 24 hours. Set
Cache-Control: max-age=3600 on the manifest response as a reasonable default — this allows agents to cache for one hour before re-fetching.Configuration examples
Minimal — just catalog and checkout
/.well-known/ucp
Full-featured store with all optional capabilities
/.well-known/ucp