agent.json Service Declaration
7.1 What Is agent.json
agent.json is a JSON file placed in your website’s .well-known directory that tells AI agents which AI interaction capabilities your site supports.
File path: https://yourdomain.com/.well-known/agent.json
Analogy: llms.txt says “who I am”; agent.json says “what I can do.” Think of it as the menu board outside a restaurant — an AI agent can glance at it and immediately know what services are available.
7.2 Why You Need agent.json
Agentic commerce is converging around multiple protocol standards (UCP, ACP, MCP, and others). Each merchant supports a different set of protocols and capabilities. agent.json lets AI agents quickly determine:- Which commerce protocols do you support?
- Where are your API endpoints?
- Do you accept AI agent-initiated orders?
- What format is your product data in?
7.3 agent.json Field Specification
Field Reference
| Field | Required | Description |
|---|---|---|
schema_version | Yes | Specification version number |
name | Yes | Brand / company name |
description | Yes | One-line description |
url | Yes | Website URL |
capabilities | Yes | Supported AI interaction capabilities |
capabilities.product_discovery | Recommended | Product discovery (UCP, etc.) |
capabilities.checkout | Optional | Checkout capability (ACP, etc.) |
capabilities.customer_service | Optional | Customer service (MCP, etc.) |
trust | Recommended | Trust verification information |
structured_data | Recommended | Structured data declarations |
policies | Recommended | Policy page links |
7.4 Configuration Examples by Merchant Size
Small Merchant (Product Display Only)
Mid-Size Merchant (Product Discovery + Customer Service)
7.5 Deployment
- Create the
.well-knowndirectory if it does not exist - Create
agent.jsoninside that directory - Ensure the HTTP response Content-Type is
application/json - Ensure robots.txt is not blocking the
/.well-known/path
| Platform | Method |
|---|---|
| Nginx | Create .well-known/agent.json under the root directory |
| Apache | Same as above; ensure the .well-known directory is accessible |
| Vercel / Netlify | Place at public/.well-known/agent.json |
| Shopify | Via App Proxy or custom routing |
| WordPress | Create .well-known/agent.json in the web root |
7.6 Verification
After deployment, check:- Visit
https://yourdomain.com/.well-known/agent.json - Confirm valid JSON is returned (use JSONLint to validate format)
- Confirm the Content-Type is
application/json - Confirm all URL links are accessible
Next chapter: Sitemap Optimization — Helping AI crawlers efficiently discover all of your pages