# Make your website readable to AI agents.

> AIS (AI Sight Protocol) is an open protocol from Juggernaut Dev that makes a website readable to AI agents. A site publishes a manifest at /.well-known/ais, an index of every page, clean content chunks with their source, a change feed, and pointers to UCP, ACP, MCP and WebMCP. The files update on every publish. AIS is free under Apache-2.0 and maintained in public by AI agents, with a person approving every change.

AIS is an open format that gives AI agents a typed index of your site, clean content with its source attached, freshness signals, and pointers to the protocols they use to act. A small set of JSON files beside your sitemap, updated automatically every time you publish.

Status: Open protocol · Apache-2.0 · Coming soon

## The problem, in numbers

- 393%: growth in AI-referred traffic to US retail sites, Q1 2026 ([Adobe](https://business.adobe.com/blog/ai-traffic-surge-retail-sites-not-machine-readable))
- 25-34%: share of homepage and product-page content language models cannot read, 2026 ([Adobe](https://business.adobe.com/blog/ai-traffic-surge-retail-sites-not-machine-readable))
- 97%: share of llms.txt files that received no requests in May 2026 ([Ahrefs](https://ahrefs.com/blog/what-is-llms-txt/))

AI agents do not run your JavaScript, do not read your layout, and guess where your content starts and ends. AIS removes the guessing.

## What an agent gets

- **A manifest at a known address.** One file at /.well-known/ais says what the site is and where everything lives.
- **An index of every page.** Every page is listed with its URL, summary, type, update time and hash.
- **Clean chunks with their source.** Content arrives split into passages with the source URL and heading context attached.
- **A change feed, so agents fetch only what changed.** Agents read what changed since their last visit and skip the rest.
- **Pointers to checkout and tools (UCP, ACP, MCP, WebMCP).** The manifest tells agents which protocols to use when they want to act.

## How it works

Publisher side:

1. Install the integration for your platform: a framework package, a CMS plugin, or a database template.
2. Run the first build. It writes the manifest, the indexes, the chunks and the change feed.
3. Run ais validate and ais score to see your conformance level.
4. Publish as usual. Each publish updates only the files for the page that changed.

Agent side:

1. Discover the manifest through robots.txt, the HTML link or /.well-known/ais.
2. Read the index and fetch only what changed since the last visit.
3. Keep the source URL on every passage and act through the protocols the manifest names.

| Standard | What it gives an agent | What AIS adds |
|---|---|---|
| llms.txt | A Markdown list of links | Types, chunks, hashes, versions and validation. AIS writes llms.txt anyway. |
| schema.org JSON-LD | Entity markup per page | A site-level index and chunked content. AIS writes JSON-LD anyway. |
| Markdown for Agents | One clean page on request | A site index, chunk boundaries and a change feed. |
| UCP, ACP | Checkout and payment | The content layer, with pointers to UCP and ACP for actions. |
| MCP, WebMCP | Tool access | A file format the AIS MCP server exposes over MCP. |

## Works with what you already run

Next.js, Astro, WordPress, Shopify, Webflow, Wix, Squarespace, Strapi, Sanity, Contentful, Supabase, Lovable

Publish as usual. The AIS files update within a minute.

## What we are building

The aisprotocol.io web app. These screens are a preview with sample data.

- **Readiness check.** Paste a URL and see how readable the site is to AI agents, with a score, a conformance level and the top fixes.
- **Live agents.** Watch the agent team that maintains AIS work through its cycle in TorqueSight, and see where a person decides.
- **Use AIS in Claude.** Connect the AIS MCP server so Claude and any MCP client can read a conformant site today.

## An open protocol, maintained in public by agents.

Every week a team of AI agents triages requests, ranks them, writes the code and opens pull requests. TorqueSight maps every step, scores every agent and shows it live. A person approves every merge, and the specification changes only through written proposals with a public comment period.

Pull requests > Triage > Rank > Human approval > Implement > Review > Human approval > Release

[See how TorqueSight works](https://opensource.juggernautdev.com/torquesight)

## Open and governed

- Code under Apache-2.0
- Specification under CC BY 4.0
- A W3C Community Group, planned at launch
- Every specification change through a public proposal

## FAQ

### Is this llms.txt?

No. llms.txt is a Markdown list of links with no types, chunks, hashes or validation. AIS generates llms.txt for you anyway.

### Do ChatGPT, Claude or Gemini read AIS today?

Not as crawlers yet. Any MCP client will be able to read an AIS site through the AIS MCP server from day one.

### Does it need a server?

No server is needed to read AIS. Static sites build the files with the site, and a CMS updates them on every publish.

### Is it free?

Yes. The code is Apache-2.0 and the specification is CC BY 4.0.

### When does it launch?

The specification, the code and the free tools open together. Leave your email to hear first.

## Get notified when AIS opens.

Leave your email at https://opensource.juggernautdev.com/ais#notify.

AIS Protocol is open source under Apache-2.0, built by Juggernaut Dev.

Part of [Juggernaut Dev open source](https://opensource.juggernautdev.com).