Skip to content
POLARGATE
Grow // Your website as something an AI assistant can query, not just crawl.

Agent surfaces

An MCP server, a public JSON API, an OpenAPI spec and a markdown twin of every page, all generated from the same data the site renders, plus a listing in the registries where assistants look for tools. The pages people read do not change. Software gets a second way in.

An older man reads his phone in a dim kitchen, a moka pot heating on the gas flame beside him and a narrow city street outside the window

What it is

Four ways to consult your website as software, plus the paperwork that makes them findable: an MCP server, a public JSON API, an OpenAPI specification, a markdown twin of every page, and a listing in the registries where assistants and their users go looking for tools.

Four ways an assistant can reach the same answer

Four ways an assistant can reach the same answerAn assistant can call a Model Context Protocol tool, fetch the JSON API, read the markdown twin of a page, or crawl the HTML. All four are generated from the same content, so none of them can disagree with the others.An assistant, answering a buyer"who builds hotel sites?"MCPasks a tool a questionJSONreads prices and cases as data.mdreads any page as plain textHTMLcrawls the page like a searchengineOne source of contentso the four never disagree
A site you can only crawl competes against a site you can question.

The pages do not change. Everything a person sees stays exactly where it is. What gets added is a second way in, built for software.

Why a crawled site loses to a queried one

When someone asks ChatGPT or Claude for a supplier, the assistant answers with what it can consult. Usually that means whatever HTML a crawler happened to fetch, some weeks ago, without running your JavaScript.

A site with agent surfaces is in a different position. The assistant calls a tool, asks for your prices, gets them back as data in the language it asked in, and quotes them. That is the difference between being remembered vaguely and being read exactly.

What gets built

The MCP server

MCP is the protocol assistants use to call tools. Your server exposes a small read-only set: list what you sell, get the price list, find a page, return one page in full. Read-only means it can face the open internet without becoming a way into anything else you run.

The JSON API and the OpenAPI spec

The same content over plain HTTP, no key. The OpenAPI file describes every endpoint, so a developer, or an agent writing its own client, can use it without asking you a single question first.

A markdown twin of every page

Each page also answers at the same path with a .md suffix: front matter, the heading, the text, no navigation and no scripts. It is what an assistant actually wants when it fetches a page, instead of a template it has to dig through.

Getting listed

The server and the API are submitted to the public MCP registries and tool directories. A tool nobody can find is a tool nobody calls.

How it stays true to the site

The surfaces are generated from the same data the pages are built from. That is the whole trick: they cannot drift out of sync, because there is no second copy of the content to keep updated. And no tool takes a URL from the caller, so the server never turns into an open proxy for somebody else's traffic.

The proof is our own site

polargate.ai runs these surfaces in public. Checked on 3 September 2026: the MCP server at /api/mcp answers a tools/list call with seven read-only tools, /api/v1 returns the site as JSON with no key and no login, /openapi.json describes that API, and every page answers at the same path with a .md suffix, across every URL in the sitemap that day.

Point your assistant at it and read what comes back. That is the same thing your buyers will do to you.

What this is not

It is not a replacement for search. The crawlers behind answer engines still fetch raw HTML and still do not run JavaScript, so the pages have to exist as real HTML first. It is not a guarantee of citations either: no one can sell that. What it does guarantee is that when an assistant tries to find out what you sell and what it costs, there is a precise answer waiting instead of a guess.

FAQ

Questions, answered

What is an MCP server, and why would my website need one?
MCP is the protocol assistants like Claude use to call tools. An MCP server on your site turns your content into a handful of read-only tools an assistant can call: list what you sell, get the prices, fetch one page in full. Crawling gives the assistant whatever HTML it happened to keep. A tool call gives it your own data, in your own wording, at the moment it asks. Polargate's server is public at polargate.ai/api/mcp, with seven read-only tools as of 3 September 2026, so you can point your assistant at it and judge the idea on the result rather than on the description.
Does this replace SEO, or is it just llms.txt?
Neither. The crawlers behind search and answer engines fetch raw HTML and never run JavaScript, so the pages still have to exist as real HTML that answers the question in its first line. That work comes first, and agent surfaces sit on top of it. And they are not llms.txt: consumer AI crawlers do not request that file, Google Search ignores it, and no study has shown a citation lift from publishing one. An MCP server and a JSON API are different in kind, because they are called on purpose by an assistant that is trying to answer a question right now, rather than left on the floor hoping a crawler picks them up.
INITIATE

Start the engine

Tell us what you are building in a few short questions. A senior engineer answers in writing within 48 business hours, with a first take on scope, timeline and price.

Start your project Talk to us