Skip to main content

Sign In

or use your email

No password needed. Your code is single-use and expires after one hour.

The Sommelier's Letter

Restaurant AI Readiness

Help customers' assistants understand your restaurant.

A customer may ask an assistant where to eat, what fits a wine budget, or which menu has a particular style. The useful starting point is accurate information: the right restaurant, a readable menu, clear serving sizes and prices, and a source the assistant can check.

Making that information easier to use does not guarantee that an assistant will recommend your restaurant, that a wine is in stock, or that a reservation was completed.

01

Readable information

A current public source with clear identity, menu sections, serving sizes, prices, and update context.

02

Supported tools

A documented interface an assistant can actually use, with clear inputs, outputs, limits, and tested clients.

03

Authorized transactions

Booking or payment through a real partner integration with explicit customer authorization.

Current capability

What RagingWine supports—and what it does not.

This table separates released website capability from work still in review or planning. We update it when a capability has been deployed and tested, not when it is merely proposed.

Public hosted wine menus

Live

Guest-facing menus publish restaurant identity, sections, wines, serving sizes, prices, and source links.

Structured restaurant and menu data

Live

Published menu pages include structured data that agrees with the visible menu.

Assistant discovery files and menu feeds

Live

RagingWine publishes concise discovery guidance plus Markdown and JSON menu representations from the same published source as the guest-facing menu.

Public API or remote MCP tools

Planned

No public remote MCP server or supported personal-assistant API is currently advertised.

Browser WebMCP tools

Planned

Browser-agent tools require supported-browser testing and a normal human fallback before release.

Booking, payment, or live inventory through an assistant

Not supported

A reservation link is a destination, not a completed booking. Published menu data is not live inventory.

Practical checklist

Keep the source accurate before adding more technology.

✓

Use the correct restaurant name, location, website, and source menu. Keep nearby branches separate.

✓

Publish the actual menu, with currency and whether each price is for a glass, bottle, or another serving.

✓

Preserve producer, wine name, vintage, region, and style when known. Leave unknown values unknown.

✓

Distinguish when content changed from when the source was verified. Neither timestamp proves live stock.

✓

Remove withdrawn menus consistently from the visible page and every supported machine-readable version.

✓

Keep drafts, customer records, billing information, and administrative tools private.

✓

Test the supported customer journey and reservation destination; do not treat a click as a booking.

An illustrative diner journey

From a question to a sourced next step.

“Find a restaurant in my city with a crisp white wine under $18 per glass, then show me where to reserve.”
  1. 1Resolve the correct restaurant and retrieve its published menu from a documented public source.
  2. 2Filter by the actual glass serving and stated currency—not a bottle price or an unknown serving.
  3. 3Recommend a menu choice only when the source supports the style and price; otherwise explain what is unknown.
  4. 4Cite the canonical menu and its update context, then open the verified reservation destination without claiming a booking.

This example explains the target workflow. It is not a claim that every assistant currently supports it.

Plain-English glossary

Six terms restaurants will hear more often.

Structured data
Labels attached to a webpage that identify the restaurant, menu, items, and serving-specific offers. They must agree with what guests see.
llms.txt
A concise guide to useful public information and its limits. It can help discovery, but it is not a ranking guarantee or access permission.
API
A documented way for software to request information in a predictable format. A public menu interface must not expose private accounts or drafts.
MCP
A standard interface through which compatible assistants can discover and use documented tools or data. It requires a real service and client setup.
WebMCP
Browser-exposed tools that may help supported browser agents use a webpage. It is different from a remote MCP service and needs a human fallback.
UCP
A protocol for defined commerce capabilities. Menu prices and reservation links alone do not establish checkout, booking, or UCP support.

Start with one accurate, maintained wine-menu source.

RagingWine's hosted menu keeps the guest-facing experience and supported public data tied to the same published menu, while restaurant owners retain a workflow for updates and review.