AIP-1 is a proposed open standard for declaring how your content
may be used by AI systems — via ai.txt, HTML meta tags,
and HTTP headers.
As AI systems become central to the web, content creators deserve a
clear, standardised way to declare their preferences. AIP-1 fills
the gap that robots.txt was never designed to cover.
AIP-1 does not restrict AI — it enables transparent communication of preferences between publishers and AI developers.
Works alongside existing standards. No infrastructure overhaul required. Add a file, a tag, or a header and you're compliant.
Designed with future AI capabilities in mind. New directives can be added without breaking existing implementations.
Built for adoption by AI labs, search engines, content platforms, and standards bodies such as the W3C.
AIP-1 operates across three complementary layers to give publishers fine-grained control at every level of the web stack.
ai.txtA plain-text file at your domain root, analogous to robots.txt, declaring site-wide AI usage preferences.
# AIP-1 Configuration File
User-Agent: *
Allow-Training: no
Allow-FineTuning: no
Allow-Indexing: yes
Allow-Summarization: conditional
User-Agent: AcademicBot
Allow-Training: yes
Allow-CommercialUse: noPer-page granular control placed in the <head> section. Overrides or supplements the root declaration.
<meta name="aip:training" content="deny">
<meta name="aip:fine-tune" content="deny">
<meta name="aip:summary" content="allow">Ideal for APIs and dynamically-generated content where HTML markup is unavailable.
AIP-Policy: no-training, no-finetune, allow-indexAll supported directives and their accepted values.
| Directive | Values | Description |
|---|---|---|
Allow-Training |
yes no | Use of content to build or improve AI models |
Allow-FineTuning |
yes no | Updating models using this domain-specific data |
Allow-Indexing |
yes no | Crawling and indexing content for AI search |
Allow-Summarization |
yes no conditional | Generating AI summaries or excerpts of content |
Allow-CommercialUse |
yes no | Use of content in commercial AI products |
Implementing AIP-1 takes minutes. Follow these steps to declare your preferences.
ai.txtAdd a plain-text file to your domain root at /ai.txt. Declare your global preferences using AIP-1 directives.
Insert <meta> tags inside each page's <head> section for page-level overrides.
For APIs and dynamic content, add the AIP-Policy response header to your server or CDN config.
Transparency is central to AIP-1. Publish a human-readable AI usage policy page for your users and partners.
Signal to the world that your site respects AIP-1. Add the badge to your README or site footer.
[](https://github.com/SquiddoTech-Systems/AIP-1/))<img
src="https://img.shields.io/badge/AIP--1-Compliant-brightgreen"
alt="AIP-1 Compliant Badge"
>
Existing mechanisms like robots.txt were designed for search
engines, not generative AI. They offer no way to distinguish between
indexing, training, fine-tuning, or
commercial use.
AIP-1 closes this gap by introducing a structured, extensible vocabulary that all stakeholders — publishers, AI developers, and standards bodies — can adopt.
View the Full Spec →