Readable information
A current public source with clear identity, menu sections, serving sizes, prices, and update context.
Restaurant AI Readiness
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.
A current public source with clear identity, menu sections, serving sizes, prices, and update context.
A documented interface an assistant can actually use, with clear inputs, outputs, limits, and tested clients.
Booking or payment through a real partner integration with explicit customer authorization.
Current capability
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.
Guest-facing menus publish restaurant identity, sections, wines, serving sizes, prices, and source links.
Published menu pages include structured data that agrees with the visible menu.
RagingWine publishes concise discovery guidance plus Markdown and JSON menu representations from the same published source as the guest-facing menu.
No public remote MCP server or supported personal-assistant API is currently advertised.
Browser-agent tools require supported-browser testing and a normal human fallback before release.
A reservation link is a destination, not a completed booking. Published menu data is not live inventory.
Practical checklist
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
“Find a restaurant in my city with a crisp white wine under $18 per glass, then show me where to reserve.”
This example explains the target workflow. It is not a claim that every assistant currently supports it.
Plain-English glossary
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.