ai.txt

Definition

ai.txt is a proposed web standard that allows website owners to declare how AI agents should interact with their site. Placed at the domain root (e.g., example.com/ai.txt), the file specifies what AI agents are permitted to do, what data they can access, and what actions are prohibited. It functions as a policy document that AI systems can read before interacting with a website.

While robots.txt tells crawlers which pages to index, ai.txt addresses a broader set of interactions: Can an AI agent browse products? Can it add items to a cart? Can it complete a purchase? Can it scrape pricing data? ai.txt attempts to give website owners explicit control over these emerging interaction patterns.

The standard is still in the proposal and early adoption phase, with no universal enforcement mechanism. But as agentic commerce grows and AI agents perform more complex actions on websites, the need for a declarative permission system becomes increasingly apparent.

Why It Matters

The rise of AI shopping agents like Amazon Buy For Me and Microsoft Copilot’s checkout feature has created an urgent problem: AI agents are interacting with merchant websites in ways that were never anticipated. They browse catalogs, scrape prices, complete checkouts, and gather competitive intelligence - often without the merchant’s knowledge or consent.

ai.txt matters because it gives merchants a voice in this interaction:

• Explicit consent model. Instead of AI agents assuming permission until denied, ai.txt allows merchants to define what’s allowed upfront. This shifts the default from “everything is permitted” to “check the policy first.”
• Granular control. Merchants can differentiate between types of AI interactions. You might welcome an AI agent that helps users discover products while prohibiting one that completes purchases without direct user involvement on your site.
• Agent identification. ai.txt can specify which AI agents are recognized and what each is permitted to do, allowing merchants to grant different access levels to different platforms.
• Legal foundation. A published ai.txt file creates a documented, machine-readable record of the merchant’s intent. If an AI agent violates the stated policy, the merchant has a clear basis for legal or technical response.
• Industry standardization. As more sites adopt ai.txt, AI agent developers face increasing pressure to respect these declarations. Network effects drive adoption - the more sites publish ai.txt, the more AI agents are built to read it.

For merchants, ai.txt is a defensive tool. It won’t stop a determined scraper, but it establishes norms and expectations that responsible AI platforms will follow. In a landscape where Amazon’s Buy For Me is listing products without merchant permission, having a published policy matters.

How It Works

ai.txt is a structured text file placed at the domain root with specific declarations:

1. Agent permissions. The file lists AI agents by name or category and specifies what each is allowed to do. Permissions can include browsing products, accessing pricing, reading reviews, adding to cart, and completing purchases.

2. Action restrictions. Specific actions can be explicitly prohibited. A merchant might allow product browsing but prohibit automated checkout, or allow price reading but prohibit competitive price monitoring.

3. Data access rules. The file can specify which data AI agents can access and use. Product descriptions and public pricing might be permitted, while customer reviews or inventory levels might be restricted.

4. Contact and escalation. ai.txt can include contact information for AI agent developers who want to negotiate different access levels or report issues.

5. Update frequency. The file can declare how often AI agents should re-check the policy, ensuring they operate under current permissions rather than cached ones.

Implementation is straightforward: create a text file following the proposed format, upload it to your domain root, and ensure it’s accessible at yourdomain.com/ai.txt. Like robots.txt, compliance is voluntary - it depends on AI agent developers choosing to respect it. But publishing the file is the first step toward establishing your store’s AI interaction policy.

Related Terms

• llms.txt - A complementary standard focused on helping AI models understand your site’s content and structure
• robots.txt for AI - The practice of adapting traditional robots.txt to manage AI-specific crawlers
• Shopify MCP - A protocol-level approach to structured AI agent access for Shopify stores
• AI Shopping Agent - The AI systems whose behavior ai.txt is designed to govern