AI agents already read your pages. Hand them the tools.
WebMCP is an open web standard (Google, Microsoft, and since August 2026 OpenAI's ChatGPT desktop browser, plus Codex and Chrome 150+) that lets a page give the agent in a visitor's browser a small set of tools to call instead of guessing at buttons. Viz generates yours from your business profile, contact form and catalog. There is nothing to write or configure, every call is logged as an agent request, and the leads and purchases that follow are credited to the agent.
The agent never checks out. The visitor does.
WebMCP tools act inside the visitor's own session: the same cart they see on the site, the same contact form you already have. The agent prepares; the person confirms. What changes is that the agent no longer has to guess where your buttons are.
From a question in the browser to a line in your ledger.
An agent arrives in the visitor's browser
Someone asks the agent in ChatGPT's desktop browser, Codex or Chrome to find a plan, check a price or get in touch. The agent opens your page the way a person would, in a browser that exposes the WebMCP API.
The page hands it your tools
A first-party inline script of about 3 KB registers your tools the moment the page loads, and only when the browser exposes WebMCP. Every other browser sees nothing and the script exits at once. No third-party requests, ever.
It calls a tool, and Viz logs it
The call goes to your own site, same-origin only and rate-limited, and is recorded as an agent request under AI Conversions → Agent tools: which tool, when, and what came of it.
You get the lead or the order
A contact_business call becomes a lead, emailed to you and stored only on your site. On a store, the agent fills the visitor's own cart; the visitor checks out, and the purchase is credited to the agent.
What an agent can ask your site, and what it can do there.
Every page registers describe_business and contact_business. WooCommerce stores with published products also register the seven shopping tools. Each one is generated, never hand-written, and each maps to one of the five questions an agent asks: describe, list, price, availability, act.
| Tool | What it answers | Reads or acts | Where it comes from | Verb |
|---|---|---|---|---|
describe_business | What you are and offer, who you serve, where a visitor can act, and which questions your site can answer | Reads | Business profile and capability map | Describe |
contact_business | Sends a contact, quote or availability request on the visitor's behalf; a person replies by email | Acts | Your contact form fields | Act |
search_products | Products matching a query: name, URL, price, stock and id | Reads | WooCommerce catalog | List |
browse_products | Products by category, on sale or featured, sorted and paginated, with the category list | Reads | WooCommerce catalog | List |
get_product | Full details for one product: variations, attributes, images and rating | Reads | WooCommerce catalog | Price |
get_cart | The visitor's own cart, as they see it on the site | Reads | WooCommerce session | Availability |
add_to_cart | Adds a product or variation to the visitor's cart and returns it with the checkout URL | Acts | WooCommerce cart | Act |
update_cart | Changes a quantity; zero removes the line | Acts | WooCommerce cart | Act |
apply_coupon | Applies a coupon code to the visitor's cart, with its own rate limit | Acts | WooCommerce cart | Act |
The read-only tools change nothing. The four that act change only the visitor's own cart or send the request they asked for, and every one of them is logged.
A tool call is an agent request. What follows it gets credited.
Leads
A contact_business call is the same request your /ai-contact/ form accepts. It becomes a lead under AI Conversions, is emailed to you, and never leaves your site.
Purchases
When an order follows an agent's tool call, Viz credits it to "WebMCP agent" the same way it credits a visit from ChatGPT: only with cookie consent, and never replacing an existing AI-referral credit.
Every call
Each call is logged as an agent request, so the Agent tools tab shows which tools agents use, how often, and which ones convert. Calls also appear in Intent, in segments and in the daily digest.
For agents that never open a browser.
Not every agent arrives inside a browser. An assistant that fetches your booking page on someone's behalf and finds only a JavaScript widget leaves with nothing. Viz publishes a plain, machine-readable contact and quote form at /ai-contact/ that an agent can read, fill in and submit for the person it is working for. The form carries the WebMCP declarative attributes too, so both kinds of agent end up in the same place.
An agent fetches a money page
ChatGPT, Perplexity and their kin already fetch pricing, booking and contact pages on people's behalf, from outside any browser. Viz sees those visits like any other request.
It finds the door
On exactly those pages, Viz points agents at /ai-contact/ with a link in the page head and a response header. Human visitors never see it; your theme never changes.
It reads a form built for machines
Every field has a name, a type, a required flag and an example. Ask for JSON and the agent gets the whole schema plus a ready-to-run request. A wrong submission gets an error that says exactly how to fix it.
You get the lead
The submission lands in your inbox, is stored only on your site, and is credited under AI Conversions with the agent that sent it. No personal data ever leaves your WordPress.
Verified on your homepage, not assumed.
A toggle can be on while a cache or a content-security policy strips the script out. So Viz does not take its own word for it: the weekly scan fetches your homepage the way an agent would and looks for the registered tools. When they are there, AI Conversions → Agent tools shows a “Verified on homepage” pill; when they are not, it says so and tells you what to purge.
Illustrative numbers. Tools register on HTTPS sites only and are on by default; Settings → Agent contact endpoint and WebMCP tools switches them off.
Early, and we say so.
Agents fetching pricing, booking and contact pages on someone's behalf is already routine. Agents calling a tool on a page is new: the browsers that support WebMCP shipped in 2026, and most visits still come from browsers that do not. We report the agent channel as what it is: real, small, and growing from a baseline you can watch in your own dashboard. The sites that are ready when it stops being small get the first requests.
Tools for agents, on your terms.
Two small scripts, both yours
Viz prints two first-party inline scripts with no external requests: one that only runs for visitors arriving from an AI assistant, and the ~3 KB one that registers your tools. Viz never loads scripts from third parties.
Same-origin, rate-limited
Calls are accepted only from your own pages, are rate-limited, and never bypass the honeypot or the lead limits your contact endpoint already enforces. Coupon attempts are limited separately.
Leads stay in your WordPress
Contact requests are stored only in your site's database, emailed to you, and covered by the WordPress personal-data export and erase tools. Nothing about a lead syncs to Viz Cloud.
Off where it should be off
Nothing is printed for logged-in editors, feeds or embeds. Sites with a strict Content-Security-Policy can allow the inline scripts or leave the feature off; the toggle lives in Settings → Agent contact endpoint and WebMCP tools.
Agent tools FAQ.
What is WebMCP?
An open web standard, backed by Google and Microsoft and consumed by OpenAI's ChatGPT desktop browser since August 2026, that lets a web page hand the AI agent in a visitor's browser a small set of named tools it can call directly, instead of guessing at buttons and forms. The page declares the tools; the agent decides when to use them; the visitor stays in charge of the session.
Do I have to write or configure the tools?
No. Viz generates them from your business profile (what you sell, who you serve, how people convert), your contact form fields and, on WooCommerce, your catalog. They are on by default on HTTPS sites. If you change your contact form or your profile, the tools follow.
Which browsers and agents can use them?
Browsers that expose the WebMCP API: ChatGPT's desktop browser, Codex and Chrome 150 and later at the time of writing, with Google and Microsoft behind the standard. In every other browser the script exits immediately and the page is unchanged.
Can an agent buy from my store?
It can search and browse your catalog, read a product in full, look at the visitor's cart, add to it, change quantities and apply a coupon, all in the visitor's own session. It never checks out. The visitor completes the purchase, and when they do, Viz credits the order to the agent.
Is this a paid feature?
No. Agent tools, /ai-contact/, agent requests and the capability map are included on every plan, including Free. Paid plans keep more history: 7 days on Free, 90 on Lite, 365 on Pro.
How do I know it is working?
Viz checks your homepage for the registered tools during its weekly scan and shows a "Verified on homepage" pill under AI Conversions → Agent tools. Below it, every tool is listed with its call count and last call. A full-page cache or a logged-in view can hide the script until the cache is purged; the pill tells you.
Does it change my theme or slow the site down?
No theme changes. The inline script is about 3 KB including the tool descriptions, is printed in the footer, and does nothing in browsers without WebMCP. It requires HTTPS, and after switching it on or off you should purge your page cache and test logged out.
How is this different from /ai-contact/?
Two doors for two kinds of agent. WebMCP tools serve the agent running inside a visitor's browser, on the page they are looking at. /ai-contact/ serves the agent fetching your site from outside, on a person's behalf, with no browser at all. Both end the same way: a lead under AI Conversions, credited to the agent.