Toast (order.toasttab.com) for AI Agents

The mapped surface covers the whole guest ordering flow. set_fulfillment switches between pickup and delivery. On the menu, search_menu filters items by name and view_category jumps the page to a named section like 'Pizza' or 'Desserts'. view_item opens an item's modifier modal, where select_modifier toggles options (size, toppings, removals) and set_quantity steps the count up or down. add_to_cart confirms the configured item and returns to the menu.

From there the checkout lane takes over: proceed_to_checkout moves to the checkout page, add_promo_code applies a code through the promo modal, set_tip sets the tip, and set_contact_info fills the guest contact form. Cart review is always available via open_cart from the header icon on any screen. Because Toast is multi-tenant, change_restaurant lets the same session compare menus or place orders at several restaurants.

These come straight from the mapped action behavior, not guesswork:

• **Required modifiers fail loudly, then recover.** add_to_cart fails if a required modifier group has no selection, and the error message names the missing group(s). The recovery loop is mechanical: call select_modifier for each named group, then retry add_to_cart.
• **Set fulfillment before browsing.** Prices and availability can differ between pickup and delivery, so call set_fulfillment before viewing items if the current mode is wrong.
• **One session, many restaurants.** Use change_restaurant with a restaurant_slug (the path segment after /online/ in the URL) instead of starting a new session per restaurant.
• **Tips are preset or custom, never both.** set_tip takes a preset percent (15, 18, 20, or 22) to click the matching button, or a custom dollar amount. Pass one or the other.
• **The menu search box starts collapsed.** search_menu expands it, types the query, and the visible item list updates in place without leaving the menu screen.

Nearly the entire surface is public. Only three actions are flagged as requiring auth: checkout, view_order_detail, and save_to_wishlist. When sign-in is needed, the mapped login entry point is https://www.toasttab.com/login.

The config also maps a guest lane: set_contact_info fills the guest contact form (email, first name, last name, phone), which is required for guest checkout. Toast does not send a confirmation OTP for those fields, so your agent fills them and moves on with no verification detour.

Instead of scraping the page, your agent calls dedicated extraction actions on each screen:

• **Menu:** extract_menu settles the page and returns data.listings, an array of {name, url, details} records. The url is exactly what view_item expects (it looks like /online/{slug}/item-{name}_{uuid}). Only fall back to extract_content if data.listings comes back empty.
• **Checkout:** extract_order_summary returns data.listing with subtotal, tax, total, and tip_options for the currently displayed order.
• **Item modal:** extract_item_modifiers returns the open item's name and URL. Toast's modifier groups (the radios and checkboxes inside the modal) are not yet exposed as structured data, so the agent reads them from extract_content's ARIA fallback; the group_uuid and option_uuid that select_modifier needs appear as {group}_{option}-input testids in the page source.