<!-- Canonical: https://wildpipe.com/developers/ai-booking -->
<!-- Last reviewed: 2026-08-30 -->

# Let your customers’ AI assistants book with you

More people now ask an AI assistant to “find someone to get the raccoon out of my attic and book it.” With WildPipe, that assistant can see your services and prices, check your real openings and book the visit, the same way a person does on your booking page. Included with online booking.

**Base address:** https://api.wildpipe.com/functions/v1/ai-assistant-booking
**Sign-in:** none. No key or account is needed.
**Reviewed:** 2026-11-18

## AI Booking and the MCP server are different things

| | AI Booking | MCP for AI |
| --- | --- | --- |
| Who uses it | Your customers’ AI assistants | Your own team’s AI tools |
| What it can reach | One business’s public booking: services, prices, openings and bookings that assistant made | Your business records, with the permissions you approve |
| Sign-in | None. No key or account | An owner or admin signs in and approves permissions |
| Where to read more | This page | MCP for AI |

## How a booking happens

1. **The assistant finds your booking details.** Your WildPipe website tells assistants how to book with you, and your booking widget has its own addresses you can give to any assistant.
2. **It reads your services and prices.** Only the services you offer online, with current prices, options, deposits and what each visit covers. You can narrow the list for assistants.
3. **It checks real openings.** The same live openings your booking page shows, checked again at the moment of booking so two people never get the same time.
4. **It confirms with the customer.** The assistant must read back the service, price, date and time, and address, and get a clear yes before it books.
5. **It books, or hands the customer a link.** When nothing needs paying or signing, the visit is booked on the spot. When a deposit, a service plan or your terms are involved, the customer gets a one-time link with everything filled in to finish it themselves.
6. **You see it like any other booking.** The booking lands in Conversations and on your schedule, labeled as booked by the customer’s AI assistant, with the assistant’s name.

## Safeguards

- **Assistants never handle card numbers.** Anything that needs a payment, a recurring plan agreement or your terms becomes a one-time link the customer opens. The link lasts 48 hours and no time is held until they finish.
- **One business only.** An address made for one business only ever talks to that business. A request that names a different business is refused.
- **The customer says yes first.** Booking, moving and cancelling all require the assistant to confirm with the customer before it sends the request.
- **No marketing consent by proxy.** An assistant can pass along the customer’s yes to appointment texts and emails. Marketing messages are only ever chosen by the customer themselves.
- **Changes follow your rules.** An assistant can look up, move or cancel only a booking it made, using a private code it received when it booked, and only within your online change rules. Paid visits and visits close to their time go to your office.
- **Retries never book twice.** Each booking attempt carries its own request id, so a repeated request returns the first result.

## What the business controls

- **How assistants may book.** Book right away when nothing needs paying or signing, always send the customer a link to confirm, or turn it off.
- **Which services.** All the services your booking widget offers, or only the ones you pick.
- **Notes for assistants.** A short note assistants read before booking, such as what to ask or what you do not do.
- **Unfinished links.** Remind the customer, tell your office, both or neither. Customers are only reminded if they agreed to appointment texts or emails.
- **Alerts.** Get told about each assistant booking, a daily summary, or nothing.
- **Results.** The Bookings tab shows visits finished, money collected, unfinished links and requests that had to be turned away, by assistant.

## Ways to connect

### From the business’s website
Websites built with WildPipe publish a plain-text guide and a small booking file that assistants look for. Nothing to set up.

```
https://your-website.com/llms.txt
https://your-website.com/.well-known/ai-booking.json
```

### As an MCP server
For assistants that support custom connectors. Each booking widget has its own address, limited to that one business.

```
https://api.wildpipe.com/functions/v1/ai-assistant-booking/mcp?widget_id=YOUR_WIDGET_ID
```

### As an API description (OpenAPI)
For custom GPTs, agents and your own code. Every request is fixed to that one business.

```
https://api.wildpipe.com/functions/v1/ai-assistant-booking/openapi.json?widget_id=YOUR_WIDGET_ID
```

### As plain JSON
One request returns the business, its booking rules, services and the addresses for everything else. A website address works when the widget id is not known.

```
curl "https://api.wildpipe.com/functions/v1/ai-assistant-booking/discover?widget_id=YOUR_WIDGET_ID"
curl "https://api.wildpipe.com/functions/v1/ai-assistant-booking/discover?domain=your-website.com"
```

Each business copies its own addresses from Booking Widgets: open a widget and find the Customer AI assistants card. The same card has step-by-step setup guides for a ChatGPT custom GPT, a Claude connector, a Gemini Gem and a Copilot Studio agent, and a check that your website points assistants to the right place.

### Example: check openings

```bash
curl -X POST https://api.wildpipe.com/functions/v1/ai-assistant-booking/availability \
  -H "Content-Type: application/json" \
  -d '{
    "widget_id": "YOUR_WIDGET_ID",
    "service_id": "SERVICE_ID_FROM_SERVICES",
    "date": "2026-12-03",
    "zip": "37209"
  }'
```

## Tools and requests (10)

- **get_business** (`GET /discover`, reads) — Business name, contact details, booking rules and how booking works.
- **list_services** (`POST /services`, reads) — Bookable services with prices, options, deposits and what each visit covers.
- **check_service_area** (`POST /service-area`, reads) — Whether the business serves a ZIP code.
- **check_availability** (`POST /availability`, reads) — Real open times for a service on a date, in the business’s time zone.
- **book_appointment** (`POST /book`, acts) — Book an opening after the customer confirmed. Returns a booking number, or a link the customer opens to pay or agree.
- **check_booking_request** (`POST /request-status`, reads) — Whether the customer finished a booking that was sent to them as a link.
- **get_my_booking** (`POST /booking`, reads) — The date, time and status of a booking the assistant made, and whether it can still be changed online.
- **check_reschedule_openings** (`POST /reschedule-openings`, reads) — Open times to move that booking to another day, with the same technician.
- **reschedule_booking** (`POST /reschedule`, acts) — Move that booking to a new opening after the customer said yes.
- **cancel_booking** (`POST /cancel`, acts) — Cancel that booking after the customer said yes.

## Rules every assistant is given

- Book only for the one customer who asked, using only the details they gave.
- Read back the service, price, date and time, and address, and get a clear yes before booking.
- Use only openings returned by the availability check. If an opening is gone, check again.
- When a time is an arrival window, tell the customer the technician may arrive any time in that window.
- Never ask for or send card numbers. Give the customer the finish link instead.
- Pass along a yes to appointment texts or emails only when the customer said it.
- Prices are the business’s current online prices; a technician may quote extra work after inspecting.
- For emergencies, tell the customer to call the business.

## Questions

### Does an AI assistant need an API key to book?
No. Booking by a customer’s AI assistant needs no key and no account, just like your public booking page. It can only reach what a customer could already see and do there.

### Which AI assistants can use it?
Any assistant that can connect to an MCP server or use an API description (OpenAPI), which covers custom GPTs, connectors, Gems and agents. Whether a given assistant offers those options depends on its maker and on the customer’s plan.

### Can an assistant take a payment?
No. When a deposit, a recurring plan or your terms are needed, the customer gets a one-time link and finishes that part themselves on your booking page.

### Can an assistant book with a different company than the one it reached?
No. Each address belongs to one business, and a request that names another business is refused.

### Can I turn it off?
Yes. For each booking widget you choose whether assistants book right away, always send the customer a link, or cannot book at all.

### Is this the same as the MCP server for AI tools?
No. The MCP server lets your own team’s AI tools work with your business records after an owner or admin signs in. AI Booking is public and limited to booking with one business.

### Does it cost extra?
No. It is part of online booking.

## Related
- [Online booking](https://wildpipe.com/features/booking-widget)
- [MCP server for your own AI tools](https://wildpipe.com/developers/mcp)
- [Guides & Webhooks](https://wildpipe.com/developers/api)
- [Developers](https://wildpipe.com/developers)
