--- title: "Toolkit: AI Browser Tools" description: "> AI Browser Tools lets the AI assistant inside a guest's browser search your homes, price a stay and start checkout on your own website, while payment and guest details stay with the guest. ## What it does More guests…" url: "https://homerunner.io/docs/toolkit-ai-browser-tools/" updated: "2026-10-08" category: "Booking & Checkout" --- # Toolkit: AI Browser Tools > AI Browser Tools lets the AI assistant inside a guest's browser search your homes, price a stay and start checkout on your own website, while payment and guest details stay with the guest. ## What it does More guests now browse with an assistant built into their browser or a desktop app. When that assistant has no way to work with your site, it falls back on what it can read, and the guest ends up on a listing platform. AI Browser Tools gives the assistant a direct way in. It is built on WebMCP, an emerging browser feature backed by Google and Microsoft. With it, your pages offer a small set of tools that the assistant can use on the guest's behalf. A guest can say "find a pet-friendly home near the lake for October 10 to 13, two adults" and the assistant does the work on your site. Four tools are available: - **Search homes**: finds homes by dates, party size, location, amenities and price. Available on every page. - **Check a stay**: prices one home for the guest's dates and party in your booking widget. Available on a home's page. The booking form on the page follows along, so the guest sees the same dates and total the assistant reports. - **Read home details**: returns the details the [AI Booking Channel](/docs/toolkit-ai-booking-channel/) publishes for a home. Available on every page. - **Start checkout**: takes the guest to checkout for the stay they just checked. Guest details and payment are never filled in for them. The reservation is made by the guest, on your checkout. A home's page offers up to four tools. Any other page offers up to two (search and details). Prices from a search are indicative. The only total an assistant states as the price of a stay is the one the stay check returns, and your checkout confirms it. ## How to turn it on ### 1. Switch on the AI Booking Channel AI Browser Tools only offers the homes the AI Booking Channel publishes, so it needs the channel on. The Hub will not let you switch AI Browser Tools on without it, and it will not let you switch the channel off while AI Browser Tools is on. See [AI Booking Channel](/docs/toolkit-ai-booking-channel/). ### 2. Switch on AI Browser Tools In the **HomeRunner Toolkit Hub**, under **AI & Integrations**, switch on **AI Browser Tools (WebMCP)**. It is off by default. ### 3. Check the status lines The **Status** section tells you whether tools are being offered. Nothing is added to your pages until every line says **Yes**: - **AI Booking Channel is on.** - **AI Booking Channel output is live.** The channel holds its output back when its kill switch is on, and on any site that is not a live production site, such as a staging copy. Nothing needs fixing on a staging copy; the tools appear on the live site. - **Site uses https.** Browsers only offer WebMCP on secure pages. Stay checks and checkout need HomeRunner 2.7.0 or later. On an older version, guests get search and home details only. The panel shows the version your site runs. ### 4. Reach more visitors (optional) The **Works with** table lists where the tools can be used today and the date each line was last checked. At the time of writing it lists: - **ChatGPT desktop app, built-in browser**: live, and needs no token. - **Chrome, WebMCP origin trial**: Chrome 149 to 162, ending March 29, 2027. Chrome offers WebMCP to everyday visitors only on sites that have joined its origin trial. Use the **Register for the WebMCP origin trial** link in the panel, then paste the token into **Origin trial token**. A token belongs to one site address, so every website needs its own. - **Model Context Tool Inspector** (a Chrome extension): a test tool for developers, not an assistant for guests. Without a token, the tools appear only in browsers that already have WebMCP switched on. ## Settings | Setting | What it controls | | --- | --- | | Search homes, Check a stay, Read home details, Start checkout | One switch for each tool. A tool you switch off is no longer offered to the browser. All four are on by default. | | Origin trial token | The token from Chrome's origin trial registration. One line of letters, digits, plus, slash and equals signs, up to 2,048 characters. Line breaks from pasting are removed. A token that fails the check is not saved and the panel tells you. The panel shows **Token saved** or **No token**. Default: empty. | | Listings page address | The page on your website that shows your property search. Search results point the guest there. Leave it empty if you have no such page. The address must be a page on this website. Default: empty. | | Count tool activity | Counts how often tools are offered and run, for the Activity section. Nothing about the guest is stored. Default: on. | ## Seeing what it does The **Activity** section shows the last 7 days. It lists what happened (tools offered, tools run, stays refused by your booking rules, errors), which tool, and how many times. Activity is kept for 30 days. A second table, **Price requests started by tools**, counts the price requests tools asked your booking system for each day. A request refused for passing the daily limit is counted there. One refused for coming too fast within a minute is not. Days are counted in UTC. **Latest problems** lists recent errors with the time, the tool and the browser, which helps when a guest says the assistant could not book. When a guest follows a **Start checkout** handoff and books, the booking is counted in the [AI Booking Channel](/docs/toolkit-ai-booking-channel/) card as an **AI Browser Tools handoff**. The same card shows an **AI Browser Tools activity** line for the window you choose, and notes that it covers the last 30 days when you pick a longer window. ## How to test With the Inspector extension: 1. In Chrome, open the flags page named in the panel and switch the WebMCP testing flag on, or save an origin trial token. 2. Install the "Model Context Tool Inspector" extension in Chrome. 3. Open a property page on your website and list the tools in the Inspector. In the ChatGPT desktop app: 1. Open a property page of your website in the app's built-in browser. 2. Ask it to check dates, for example: check October 10 to 13 for two adults. 3. Watch the booking form on the page follow along. The dates and the price it reports appear in the form too. ## Tips - Pair this with the [AI Booking Channel](/docs/toolkit-ai-booking-channel/): the channel serves assistants that read your site, and AI Browser Tools serves assistants that act on it in the guest's browser. - If your site uses the [Guest Picker](/docs/toolkit-guest-picker/), adults, children and pets are priced separately, and a pet count narrows a search to pet friendly homes. Without it, a stay is priced for one total guest count. - If a tool you expect is missing on a page, check the three status lines first, then check that the page is a home's page for stay checks and checkout. - Set the **Listings page address** so search results can send the guest to your search page.