Make your website usable by AI agents that book and buy

1. 01Done

   List the jobs customers come to your site to finish

   Two or three, no more. Request a quote. Book a consultation. Buy the thing. Check whether you do a particular job in their area. These are the jobs an AI agent will be sent to do on a customer's behalf.

   Greg Isenberg's framing of why this matters: SEO was about Google understanding your page, AEO was about AI citing you, and WebMCP, a standard from Microsoft and Google, is about the agent actually finishing the job.

   Checkpoint

   Two or three jobs, each one a thing a customer finishes.

   Copy step as prompt

   ---

2. 02Done

   Mystery-shop your own site with an agent

   the step that pays off

   Give an AI assistant that can open and use web pages the prompt below, once per job. It stops short of submitting anything, so nothing real gets booked.

   This is Isenberg's "agent mystery shopper" idea, turned on your own site: test whether an agent can complete the jobs that matter, then write down where it got stuck, which tools were missing, which descriptions were bad. Is Agentic, in our directory, scores a site's readiness for agents and gives recommendations, which is a quick second opinion.

   Send an agent to finish one job on your site

   Copy

   Go to {{YOUR_WEBSITE_URL}} and try to complete this task as a customer
   would: {{THE_JOB}} (for example: request a quote for a kitchen repaint,
   or book a consultation next Tuesday afternoon).
   Rules:
   - Stop before anything that sends a message, takes a payment or makes
     a booking that a real person would act on. Describe the final screen
     instead of submitting it.
   - Do not use search engines or other websites. Only this site.
   - Do not enter any personal details. Where a form needs them, note the
     field and stop there.
   Then report, in this shape:
   1. Finished or not finished, and at which step you stopped.
   2. Each step you took, one line each.
   3. Every place you had to guess: a button with an unclear label, a
      form field with no hint, a price or time you could not find, a
      page that needed scrolling or waiting to find the next action.
   4. What would have let you finish without guessing.

   Pro tip

   Run each job twice. An agent that finishes once by luck and fails the second time is still guessing.

   Checkpoint

   One report per job, with every guess the agent had to make.

   Copy step as prompt

   ---

3. 03Done

   Write the actions an agent should call directly

   Isenberg's plainest line on WebMCP: "WebMCP is basically websites with agent buttons. (In the margin: the whole idea.)" Instead of an agent scanning a page like a human, taking screenshots and guessing where to click, the site tells it how to search, how to book, how to buy.

   Those buttons need words. Paste your jobs, the mystery-shop reports and your business facts into the prompt below. The descriptions are the part to read closely: an agent picks an action by its description, and a vague one is the "bad descriptions" failure in Isenberg's list.

   Write the spec for the actions an agent should call

   Copy

   Write a specification for the actions our website should offer to AI
   agents directly, so an agent can complete the jobs below without
   clicking through pages. A developer will build from this.
   For each job, write one action with:
   - Name: a short verb phrase, such as request_quote or book_consult.
   - Description: one or two sentences an agent reads to decide whether
     to use it. Say what it does and when not to use it.
   - Inputs: each field, its type, whether it is required, and the
     allowed values where there is a fixed list.
   - What it returns: the confirmation, the price range, or the next
     available times, and in what form.
   - Human step: anything a person on our team must confirm before it
     becomes real (a booking, a price, a payment).
   Rules:
   - Use only the services, prices, hours and rules in the facts below.
     Where an action needs a fact that is not there, write [ASK: the
     question] instead.
   - Nothing in the spec takes a payment or confirms a booking without
     the human step.
   Jobs, and what the mystery-shop reports found:
   """
   {{JOBS_AND_REPORTS}}
   """
   Our facts (services, prices, hours, booking rules):
   """
   {{BUSINESS_FACTS}}
   """

   Checkpoint

   A spec with one action per job, each with a human step where money or a booking is involved.

   Copy step as prompt

   ---

4. 04Done

   Hand the spec to whoever builds your site

   Give the spec to your developer or site builder and ask what it takes to offer those actions to agents on your platform. Isenberg's list of first tools for a business site is short: request a quote, book a consult. Start there even if the spec has more.

   Keep the human step in whatever gets built. An agent can request the quote. A person on your team confirms it.

   Checkpoint

   The first one or two actions live, with a person confirming each result.

   Copy step as prompt

   ---

5. 05Done

   Mystery-shop again after the change

   Run the same prompt against the same jobs. Compare the reports with the first ones: the steps, the guesses, whether it finished. Keep both reports. They're the before and after for this change and the baseline for the next one.

   Checkpoint

   Two reports per job, before and after.

   Copy step as prompt

← All use cases