Publish your actions where agents look.
Gateway is designed to host what your site can already do as things an agent can call: check availability, request a quote, book a job.
01Why it matters
An agent looks for a machine-readable way in before it looks at your page.
On almost every service site there is nothing to find. Gateway is designed to give it one without touching your design, your CMS or your forms.
# 1. ARD catalogue, served at a known address
GET /.well-known/ai-catalog.json
# 2. WebMCP, declared by the page to the browser
navigator.modelContext
# 3. MCP, a hosted endpoint that outlives the tab
a persistent URL, hosted by us. No address is assigned yet.02How it works
01
Map
A browser opens your site and writes down every action it can find, with the fields each one needs.
02
Publish
One map, three formats: the catalogue file agents check at a known address, the tools a page declares to a browser, and a hosted endpoint an agent can connect to.
03
Keep it current
Hosted, so the tools stay callable after the tab closes.
03In detail
Three standards, and what we found
| Standard | What Gateway would publish | Found on the fifteen |
|---|---|---|
| ARD catalogue | A catalogue file at /.well-known/ai-catalog.json | 0 of 15 |
| WebMCP | Tool declarations the page hands the browser | 0 of 15 |
| MCP | A hosted, persistent endpoint an agent can connect to | 0 of 15 |
04Evidence and limits
15 of 15
Sites publishing no WebMCP declaration, no MCP endpoint and no ARD catalogue. The standards shipped; the implementation did not.
Gateway is not something you can switch on yet.
What you can do today is find out what an agent can and cannot do with your site.