Skip to main content
The /.well-known/ucp file is the entry point for AI agents discovering your store. It tells agents where your product catalog, checkout, shipping, and order endpoints live. You can build this file by hand, but the Manifest Generator API creates a correctly structured manifest from your endpoint URLs, validates reachability, and flags missing optional capabilities that affect agent behaviour. All calls require authentication — see Authentication.

Endpoints


Generate a manifest

Request parameters

string
required
Your store domain, without https://. Example: "yourstore.com"
string
required
Full URL of your product catalog endpoint. Example: "https://yourstore.com/api/ucp/products"
string
required
Full URL of your checkout creation endpoint. Example: "https://yourstore.com/api/ucp/checkout"
string
Full URL of your shipping options endpoint. Declaring this allows agents to calculate shipping costs before confirming a purchase.
string
Full URL of your order status endpoint. Declaring this allows agents to check order status on behalf of the customer.
Set to true if your catalog endpoint supports ?q= search queries. When false or omitted, agents will not attempt to search your catalog — they will only browse.
string[]
List of filter parameters your catalog endpoint accepts. Example: ["category", "price_range", "availability"]
string[]
Payment methods your checkout endpoint accepts. Example: ["card", "paypal", "upi"]
Example request:

Response fields

string
Manifest schema version. Always "1.0" for current implementations.
string
ISO 8601 timestamp of when this manifest was generated.
string
The domain this manifest belongs to.
object
The capability map that AI agents use to discover your endpoints.
object
Product catalog capability, including endpoint URL, format, search support, and supported filters.
object
Checkout capability, including endpoint URL, HTTP methods, authentication requirements, and supported payment methods.
object
Shipping capability (present only when shipping_endpoint was provided).
object
Order status capability (present only when orders_endpoint was provided).
Example response:

Write the manifest to .well-known/ucp

Save the API response directly to your /.well-known/ucp file. Strip generated_at so the file is stable across deployments:
The file at /.well-known/ucp must be served with Content-Type: application/json and must be publicly accessible without authentication.

Validate an existing manifest

Use this after deploying to confirm your manifest is reachable and all declared endpoints respond correctly.

Request parameters

string
Public URL of your deployed manifest. Example: "https://yourstore.com/.well-known/ucp"
object
A manifest object to validate directly, without fetching a URL. Useful for validating before deployment.
Validate by URL:
Validate an object directly:

Validation response

When valid:
When invalid:

Code examples