/.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
| Method | Endpoint | Description |
|---|---|---|
POST | /api/manifest | Generate a new manifest |
POST | /api/manifest/validate | Validate an existing manifest URL or object |
Generate a manifest
Request parameters
Your store domain, without
https://. Example: "yourstore.com"Full URL of your product catalog endpoint. Example:
"https://yourstore.com/api/ucp/products"Full URL of your checkout creation endpoint. Example:
"https://yourstore.com/api/ucp/checkout"Full URL of your shipping options endpoint. Declaring this allows agents to calculate shipping costs before confirming a purchase.
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.List of filter parameters your catalog endpoint accepts. Example:
["category", "price_range", "availability"]Payment methods your checkout endpoint accepts. Example:
["card", "paypal", "upi"]Response fields
Manifest schema version. Always
"1.0" for current implementations.ISO 8601 timestamp of when this manifest was generated.
The domain this manifest belongs to.
The capability map that AI agents use to discover your endpoints.
Product catalog capability, including endpoint URL, format, search support, and supported filters.
Checkout capability, including endpoint URL, HTTP methods, authentication requirements, and supported payment methods.
Shipping capability (present only when
shipping_endpoint was provided).Order status capability (present only when
orders_endpoint was provided).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
Request parameters
Public URL of your deployed manifest. Example:
"https://yourstore.com/.well-known/ucp"A manifest object to validate directly, without fetching a URL. Useful for validating before deployment.
Validation response
When valid:Code examples
Related
- Manifest Generator tool — browser UI version of this API
- .well-known manifest deep dive — full manifest spec and advanced options
- Readiness API — full domain audit including manifest validation