Your website, ready for AI agents. No rebuild required.
One Apache module lets AI agents read every page, ask questions, and do anything a visitor can do by clicking, in plain English, while logins stay private.
{
"type": "chat",
"protocol": "ai-chat/1",
"at": {
"url": "/shop/",
"title": "Bluewhite shop"
},
"you_can": [
{
"name": "Search",
"do": {
"form": 1
}
},
{
"name": "Add to basket: Whale widget - 29 EUR",
"fields": [
{
"label": "Quantity",
"choices": [
"1",
"2",
"3"
]
}
],
"do": {
"form": 2
}
}
],
"you_can_go": [
{
"text": "Basket",
"go": "/shop/cart.php"
}
]
}Why
“Web servers spend enormous effort making pages beautiful for humans. For utility, the content type can simply be chat: the AI and the web server hold a conversation, and the server offers a set of resources the agent uses. Browsers will gain a plugin, and eventually native support, that turns browsing into a chat interface or a hybrid of chat and HTML.”
What it does
Read, discover, ask, act and chat. On any site.
Load the module and every site on the server speaks to agents. Nothing on the site has to change.
Read
Every page exactly as people see it, or explained in English, or as clean Markdown.
Discover
An English sitemap of the whole site, plus llms.txt, generated automatically.
Ask
Agents ask in plain English; your site answers from its own content. Its AI only switches on once it knows your site.
Act
Search, forms, log in, add to basket, check out: everything a person does by clicking, done for real.
Chat
Any page can become a conversation: “You're in the shop. You can search, add the whale widget to your basket, or check out.”
Works with Claude & ChatGPT
Every site is also an MCP connector: paste one URL into your assistant and it can browse and act on the site.
Browser extension
Chat with any supporting site beside the page, in Chrome, Brave, Edge, Opera, Firefox and Safari.
Fair to advertisers
Ads reach agents too, always clearly labelled “Sponsored” and never mixed into answers.
How it works
One server, three kinds of visitor.
People get HTML. Agents and plugins get the same site as a conversation, produced from the real response.
Apache + Webserver For AI
- • learns public pages (never anything behind a login)
- • reads your code to find login-only pages
- • optional: your AI provider for open questions
Your site, unchanged
PHP, WordPress, Node, Laravel, static…
Trust
An AI interface must never become a back door.
Every rule below is enforced by the module itself, and tested end-to-end against a real shop with sessions and CSRF tokens.
Read the security model- Logins are never bypassed. Agents act with their own session, like a browser.
- Nothing behind a login is ever learned, cached, listed or shown to an AI. The module even reads your PHP and JavaScript code to know which pages need a login.
- Payments, deletions and password changes always need explicit confirmation.
- Agents keep their real IP address, so your IP rules still apply.
- Cross-site request forgery protection is built in.
- Audit logs record what was done, never what was typed.
- Advertising is passed on honestly: labelled “Sponsored”, kept out of content and AI answers, with counted impressions and clicks.
- Open source, runs on your own server, works with your choice of AI provider (Anthropic, OpenAI or any compatible API) or none at all.
Install
Three commands. Then curl it.
Debian, Ubuntu, RHEL and Fedora. Works for static sites and dynamic ones: PHP, CGI, WordPress and reverse-proxied apps.
sudo apt install apache2-dev libcurl4-openssl-dev
make && sudo make enable-debian
curl https://your-site/.well-known/aiComparison
How is this different?
| Webserver For AI | Markdown-for-agents (CDNs, plugins) | NLWeb | WebMCP | |
|---|---|---|---|---|
| Works without changing the site | needs data ingestion | needs code in the site | ||
| Readable pages for agents | ||||
| Q&A in English | ||||
| Do actions (forms, login, checkout) | server-side | in the browser | ||
| Conversation on any URL | ai-chat/1 | |||
| Usable from Claude / ChatGPT (MCP) | built in | |||
| Browser extension | all major browsers | native (Chrome preview) | ||
| Ads relayed and labelled | ||||
| Knows which pages need login | reads PHP/JS code | |||
| Runs on your own server | Apache module | CDN / CMS | separate service | browser |
We plan to publish our action catalog as WebMCP tools, so these approaches work together.
Make the web conversational.
Install the module, read the protocol, or be first to try the browser plugin.