Shipt for AI Agents

The mapped surface follows the real shopping loop on Shipt. Your agent starts on the landing screen, calls select_store to pick a retailer, then searches with search_products, which returns structured product data (name, price, size) and can include images when you pass include_images. From a result it calls view_product for detail, add_to_cart to put an item in the basket, update_quantity or remove_from_cart to adjust it, view_cart to review, and checkout to proceed. Paging is explicit with next_page and prev_page, and go_back returns to the shop page.

Beyond shopping, the config maps signed-in account surfaces: view_order_history and view_order_detail for past orders, and update_address to set the delivery address. The address action handles the whole flow itself: it navigates to the address page, types the address, selects from autocomplete, and submits.

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

• **Store scope is sticky.** select_store scopes everything that follows. All subsequent searches and cart actions run against that store, so have your agent pick the retailer before it searches, and re-select if the user switches stores mid-session.
• **add_to_cart adds exactly 1 unit.** Pass the product name or a distinctive substring as item. For more than one, follow up with update_quantity, which takes item and quantity.
• **Search before you view.** view_product expects a product name, so call search_products first to get names, then pass one back as item.
• **Filters are dynamic.** The filter set depends on the selected category, so the config exposes list-filters actions (for example list_available_filters_product_detail) that read the filters on the current listing page. Your agent should call them in context rather than assume a fixed set.

Browsing is public: your agent can select a store, search products, and open product detail without an account. Adding to the cart, viewing it, and everything past it are auth-gated: add_to_cart, remove_from_cart, view_cart, checkout, update_address, view_order_detail, and view_order_history are all marked requires_auth in the config. update_quantity is the one cart action that carries no requires_auth flag in the config.

The login action signs in at shop.shipt.com/login with email and password. Two things can happen along the way, and both are handled: Shipt may prompt to skip passkey enrollment, and it may email a 6-digit verification code when it sees an unrecognized device. That code goes into the Rindler Connect form, so the human stays in the loop for the one-time code without ever pasting credentials into a chat.

Every response tells your agent which screen it is on, and the Shipt config names 7: landing, shop, search_results, product_detail, cart, checkout, and order_confirmation. That means the agent always knows whether it is looking at a results page, a single product, the cart, or a confirmed order, and which actions apply there.

Data comes back structured rather than as raw markup. search_products returns product records with name, price, and size, and both it and view_product accept include_images when the agent needs visuals. The agent never parses Shipt's HTML; it reads records and dispatches the next action.