Agent commerce: when AI assistants become your booking channel
Tom Okonkwo
The first wave of AI search changed how customers find you. The second wave changes how they buy from you. AI assistants can now act — check availability, request quotes, create bookings — through a protocol called MCP (Model Context Protocol). A business that exposes booking tools over MCP is a business an assistant can close for, not just recommend.
From citation to transaction
Picture the whole journey inside one conversation: a homeowner asks about a failing water heater, the assistant cites your answer page, the homeowner says 'can they come Thursday?', and the assistant calls your check_availability tool, then create_booking. No website visit. No phone tag. The conversation is the funnel.
Every BookRails tenant gets a generated MCP server with exactly three tools: check_availability, create_booking, and request_quote. Bookings require an idempotency key, so a retried request can never double-book a slot.
Registries are the new maps listing
Assistants discover MCP servers through registries — Smithery, PulseMCP, Glama, mcp.so and more. Being listed is the agent-commerce equivalent of being on Google Maps in 2008: early, cheap, and disproportionately valuable. BookRails submits your server to the major registries automatically and tracks listing status.
The businesses that treat assistants as a first-class channel — with real availability, honest quotes, and fast confirmation — will own this the way early adopters owned local search.
Want pages like this on your site — fact-gated and cited?
Start your first BookRails run →