Tools your agent can call.

Search live Reuben venues by locality, feature tags, and booking rules (large-group handling, cancellation policy). Each result carries a machine-readable booking_policy block, so agents can spot instant-confirm venues right in the results. Call this first to discover which venues exist, what they offer, and their venue_id.

Already found one or more venues through your own web search? Ask Reuben whether they're bookable here, by website or name — check one, or pass a queries array to check several candidates in a single call. The answer is honest: a confident match returns the venue_id to book with; anything uncertain lists candidates without guessing; no match is a plain no. Venues can also publish /.well-known/reuben.json on their own site so agents discover the link straight from the source.

Get the full profile for one venue: name, address, phone, opening hours, booking rules, and features.

Retrieve a venue's booking rules before you commit: max instant party size, how large groups are handled, and cancellation terms.

See a Reuben-hosted venue's open slots for a date — remaining capacity, service (like Dinner), and whether each slot confirms instantly — so you can pick a real time instead of guessing. Venues that run their own diary say so honestly rather than inventing slots.

Request a table reservation — this submits a real booking request the venue acts on, and retrying is only safe with the same booking reference. Returns confirmed, pending, unavailable (with re-checked alternatives), requires-human (routed to the venue's team), or a validation error — the venue owns the outcome, and a human always owns the final yes on big asks.

Check the current status of a booking you made earlier — including requests sitting with the venue's team — using the booking reference and the original booking details. It never creates, changes, or duplicates a booking.

Get the orderable menu for a venue that does takeout — categories, items, variations, and prices straight from the venue's own point of sale, so an agent can't invent an item or a price.

A guest's own usual order at a venue that remembers its regulars, so an agent can offer "the usual?". Strictly self-scoped: keyed by the guest's own email or phone, it returns only their own repeated items — never anyone else's data — and only at venues that have said they remember regulars' usual orders.

Place a takeout (pickup) order built from the venue's live menu — a real order the venue starts preparing. The order lands on the venue's own rails, the guest gets a confirmation email, and payment is settled at the venue on pickup. Returns an order reference — save it to check on the order later; retrying is only safe with the same reference.

Check on a takeout order using just its order reference — received, preparing, ready, completed, or cancelled. Guests also get an email when the pickup status changes.

Cancel a takeout order before the venue completes it — final once done, though asking again for an already-cancelled order is harmless. Since payment is settled at pickup, a cancelled order means nothing is owed. If it's too late to cancel automatically, you're told to contact the venue instead.

Free-text search over live venues and their takeout menus — the standard discovery contract connector clients like ChatGPT require. Venue names, suburbs, feature words, and menu items all match; results carry ids to hand to fetch. Prefer find_venues when structured filters are available.

The full document behind a search result id — a venue's complete profile (hours, contact, booking rules) or its live takeout menu, served as a short action guide plus the same canonical JSON the dedicated tools return.