Let their agent take the next step.
Agent Actions let a buyer’s AI agent ask your site, check you’re the fit, and request a consultation, an estimate or a callback, on your page or from its own servers. Nothing reaches you without the person’s go-ahead.
The form, replaced by a tool call.
Until now, an agent acting for someone on your site had two options: read the page and guess, or try to fill in a contact form built for a person. Agent Actions give it a third. Your site declares what can be done — request, call back, check fit — and the agent does it with the values it already gathered, instead of retyping them into fields.
Browsers are starting to let a page offer actions to the agent on it: the ChatGPT desktop browser
does today, and Chrome is testing it. Agents that work from their own servers call the same
actions at your site’s /mcp, and answer engines that only read your pages are served
the facts your Agent Concierge publishes.
When their agent acts for them.
Not every agent opens a browser. Personal agents and chat connectors call your site’s /mcp from their own servers, often while nobody is watching, and they are let in without a key.
Built for the personal assistants now acting for buyers.
What it can do
Read your answers, check whether you take the matter on, and request a consultation, an estimate, a callback or a demo for the person. With their details and their go-ahead, it completes the request and gets a reference to tell them.
What it cannot do
It cannot opt anyone into your marketing; only the person’s own tick does that. One contact can complete five requests a day with you, and agents that call too fast are told to wait.
What it never sees
Visiting agents see your public tools only. Your analytics, audiences and campaign controls answer only to you.
Two ways to say yes.
When the person is on your page, they confirm on a card in your brand. When their agent is working alone, it completes the request for them with their details and their go-ahead.
- Nothing reaches you without their go-ahead, and every lead says how it was given
- The card is for the person. The tool is for their agent
- Their agent gets a reference back to read to them
- A time is always a second step, so the person or their agent picks it
# the tool, in the words their agent reads
Fill every fact the person already stated. If you are acting for the
person and already have their name, a phone or email, and their
agreement to be contacted about this request, send those too
(consent_contact = true) … Otherwise do not ask for identity or
consent here — the response returns a reference and a confirm step
(confirm_request) that collects them.
# what their agent gets back
Confirmed. Reference IA-7KQ2ZM. The business has your request and
will respond within one business day.Up to eight tools, in the order that matters.
An agent is offered at most eight tools on a page, so the order is deliberate. Each one is marked as a lookup or an action, and only the tools that fit your business are offered.
- Every action tool first — the request, the callback, the time
- Then the briefing, then a question-answering tool
- Then the fact that matches the page the agent is on
- A site with eight or more actions fills the budget with actions alone
Three ways onto your site.
The plugin and the Worker put /mcp and the agent files on your own domain, and each connects with a one-time code. A script tag adds the tools on your pages only.
| WordPress plugin | Cloudflare Worker | Script tag | |
|---|---|---|---|
| What it puts on your site Only the plugin and the Worker give agents /mcp on your own domain. | /mcp, llms.txt, the agent files and the page script | The same, relayed on your own domain | The page script only |
| How it connects | A one-time install code; the relay key stays on your server | A one-time install code; the key goes straight into the Worker’s secrets | Your account ID in the tag |
| If we are slow or unreachable | Answers seen before come from a saved copy; your pages are unaffected | Agent paths answer 502 after 8 seconds; your pages never depend on us | The script loads asynchronously; your pages are unaffected |
| Best for | WordPress sites | Sites whose DNS is on Cloudflare | Other site builders, for the tools on the page |
Agents find your tools on your own domain: /.well-known/mcp.json points them to
/mcp. The provider index can list the same tools
as well; it is opt-in, and off until you switch it on.
Go live, proven from outside.
Each step counts as done only when a check from outside proves it, never because a setting was saved. We run our own site this way.
# 1. agents are pointed at your tools
curl -s https://your-domain.com/.well-known/mcp.json
# 2. the tools an agent working from its own servers is offered
curl -s -X POST https://your-domain.com/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Asked and answered.
What are Agent Actions?
What a buyer’s AI agent can do on your site: read your answers, check whether you are the fit, and request a consultation, an estimate, a callback or a demo for the person. The agent acts with what it already gathered in its conversation, instead of trying to fill in a form built for a person.
Which agents can use them?
Browsers are starting to let a page offer actions to the agent on it: the ChatGPT desktop browser does today, and Chrome is testing it. Agents that act from their own servers, such as personal assistants and chat connectors, use the same actions at your site’s /mcp, and answer engines that only read your pages are served the facts your Agent Concierge publishes.
Is registering the tools the whole job?
No. Registering tools is the easy part. What matters is what happens once one is called: whether the request carries the person’s own words and their go-ahead, reaches your team with what their agent asked first, and stays on the record in your workspace.
What stops an agent from sending a request on its own?
A request reaches you only with a name, a way to reach the person and their go-ahead, confirmed on the card in your page or relayed by their own agent, and every lead records which. One contact can complete five requests a day with you, and an agent can never opt anyone into your marketing.
Should I turn on the switch Cloudflare offers for this?
No, leave it off. Cloudflare’s own switch (AI → Agent Readiness → WebMCP) strips the annotations that mark a tool as an action, and it makes our page script stand down, so the card never appears on your page. The Cloudflare Worker puts the same actions on your own domain without it.
Where do agents find my tools?
On your own domain: /.well-known/mcp.json points them to /mcp, and the page script registers the tools on your pages. The provider index can list the same tools too; it is opt-in and off until you switch it on.
See what an agent can do on your site today.
The audit checks whether your pages register tools, and what an agent could do with them. It takes a URL.