One install. Your site, on the agent web, this week.
Nothing to add to your pages and nothing to learn. We take your sitemap and give you back an endpoint any agent can use, discovery files for your domain, a registry listing under your name, and a log of every agent that shows up.
Two ways in, and one of them is free
Install the plugin and you are on it
It serves the endpoint from WordPress itself using WordPress's own search, publishes the discovery files, welcomes the answer engines by name, and keeps your log of which AI clients came and what they asked. No model is called, so nothing is billed and no key is needed.
We give it away because a web where sites can answer is worth more to us than a licence fee.
Get the pluginWe install and run it
Any site, any stack. Semantic search rather than keyword matching, so a question phrased in nobody's words still finds the right page. Registry listing under your own domain, the monthly report, a place in the trust commons, and somebody watching it.
Start with the audit: it measures what AI says about you now and again after, so the fix is proven before you commit.
See pricingThe free plugin is deliberately not crippled. The paid thing is not the layer, it is the difference: better retrieval, the accuracy report with your name on it, and somebody to call.
What happens, in order
- 1Send the sitemap
That is the whole input. Your pages are read as they are; nothing on your site changes.
- 2Your pages become an endpoint
A hosted agent endpoint answers questions from your pages in plain language, with sources. Standard MCP over HTTP. Any agent that speaks the protocol can use it, and the big ones do.
- 3Your domain says so
Two small files go at your domain: /.well-known/mcp.json and agent-card.json. Your llms.txt points at the endpoint. Agents that look at your site find the door.
- 4Listed where agents look
Your endpoint goes into the official MCP registry under your own domain name, verified by a DNS record you control. The directories that crawl the registry pick it up from there.
- 5Your own log
Every AI crawler, AI referral and agent call to your site, classified by purpose, with the client's name and whether the call worked. Hashed, never a raw address. A report whenever you want it.
- 6In the trust layer
Agents that call you can record what happened in the shared commons, and other agents read it before choosing. Your log is what the record is checked against. Honest sites win here by default.
What you need
- A sitemap. Nearly every site has one; if yours does not, a list of URLs works.
- One DNS TXT record at your domain, so the registry listing is provably yours. We give you the exact line.
- Somewhere to put two small static files, or let us host them and point a subdomain at it.
What it is not
- It does not change your search rankings or your place in AI overviews, and we do not measure or claim either.
- It does not rewrite your pages, add scripts to them, or need access to your CMS.
- It does not send your visitors' data anywhere. The log records the client that called, not the person.
- It is not a chatbot widget. It is the door agents use, on the side of the house agents come to.
Under the hood, for the technical reader
The endpoint is an instance of NLWeb, Microsoft's open conversational layer for websites, run per site on Google Cloud Run with your pages embedded into a local vector store. We changed four things: memory that reaches retrieval, a fix so unscoped questions work on a hosted single-site instance, the attestation commons, and the measurement layer. Standard protocols throughout: MCP for calls, A2A agent cards and mcp.json for discovery, llms.txt for the map. You can leave with your endpoint and your data at any time.
Running cost is close to nothing while idle and about a cent per question answered. The pilot price covers it with room.