tate@programs ~/services/agent-booking-readiness hotels / restaurants / direct booking / public proof

May 2026 / AI Mode / UCP / MCP / direct booking

Outside proof for the booking surfaces agents will touch first.

Google is moving agentic commerce beyond retail into hotel booking and food delivery. This packet checks whether a hotel, restaurant, booking engine, delivery partner, or hospitality agency surface is readable enough for agents before guests try to book, order, compare policies, or hand off payment.

send surface pay $750 after scope sample format market signal

packet: $750
partner support: $2.5k+
default: public only

booking.proof.run

$ readback hotel-or-restaurant
GET /llms.txt
GET /agents.md
GET /.well-known/ucp
GET /.well-known/mcp/server-card.json
CHECK rates, menus, availability claims
CHECK policies, fees, cancellation, delivery
CHECK booking or order boundary
WRITE buyer-safe proof packet

Fixed scope

One approved surface, one proof packet.

The goal is not to mutate reservations or orders. The goal is to prove what public agents can safely discover, where the booking/order boundary starts, and what needs patching before a guest-facing launch.

Booking readiness packet

$750

One hotel, restaurant, booking-engine, agency, or demo surface. Includes public discovery, schema and sitemap notes, policies, rates/menu signals, booking or order boundary, patch order, and re-check.

Scope packet Pay after scope

Partner support

$2,500+

White-label support for hospitality agencies, booking engines, PMS/CRS vendors, restaurant platforms, and direct-channel teams with multiple client surfaces.

Scope support

Public boundary

strict

No login, no reservation creation, no food order, no checkout, no payment, no loyalty account, no guest-data lookup, and no private endpoint testing without explicit authorization.

Ask scope

What gets checked

Agent booking breaks where public claims meet real constraints.

general proof lane

discover

Machine-readable entry

llms.txt, agents.md, UCP profiles, MCP server cards, agentic sitemaps, robots, and markdown or JSON fallbacks.

inventory

Rooms, menus, rates

Whether public pages expose stable names, availability claims, menu items, room attributes, price context, fees, and update boundaries.

policy

Guest trust signals

Cancellation, refund, delivery, dietary, pet, accessibility, check-in, support, and fee policies in forms an agent can cite without guessing.

action

Booking and order boundary

Where public discovery stops and authorized booking, reservation, order, payment, guest, or loyalty flows begin.

handoff

Patch order

A short ranked fix list for content, schema, discovery files, endpoint responses, public proof, and any authorization-only follow-up.