Allbirds for AI Agents

The core shopping loop is fully covered. Your agent calls search_products with a query, then narrows with filter_results and sort_results on the results page. view_product opens a specific result by index, view_reviews pulls up its reviews, and select_variant picks a size before add_to_cart puts it in the basket. Cart management is there too: view_cart, update_quantity, and remove_from_cart.

Beyond the cart, the config reaches into the account side of the store: checkout, promo codes, order tracking, cancellations, returns, wishlist, saved addresses, payment methods, and the Allbirds loyalty program (viewing status and redeeming points). There is also a mapped path to the store locator and a category browse from the landing page. None of this is scripted per task; each action is a stable, named capability your agent composes at run time.

These come straight from how the site actually behaves, encoded in the action descriptions:

• **Size before cart.** add_to_cart adds the currently viewed product from its detail page, and products that require a size need select_variant called first. Agents that skip the size step will not get the item into the cart.
• **Sign-in is a two-step code exchange.** Allbirds uses a passwordless Shopify new-customer-accounts flow. request_login_code submits the email, the site sends a 6-digit code, and submit_login_code finishes the job. There is no password to manage.
• **Category browse is scoped.** The mapped browse_category action navigates to the women's category page from the landing page. For anything else in the catalog, search_products is the reliable entry point.
• **Quantity only goes up.** update_quantity increases an item's quantity in the cart. To reduce a line, remove it with remove_from_cart and re-add what you want.

Browsing, product detail, reviews, and the whole cart flow are public. Your agent needs no account to research products or assemble a cart.

13 of the 29 actions require auth: checkout, apply_promo, order flows (track_order, cancel_order, return_order, view_order_detail, view_order_history), wishlist (save_to_wishlist, view_wishlist), loyalty (view_loyalty_status, redeem_points), and account settings (account_addresses, account_payment_methods).

Auth itself is passwordless email OTP at allbirds.com/account/login. The 6-digit code emailed to the user is entered in the staged Rindler Connect form; there is no browser handoff. In practice: the agent calls request_login_code with the user's email, the user reads the code from their inbox, and submit_login_code with that otp completes sign-in. From there the session is authenticated for the account actions above.

The config models allbirds.com as six screens: landing, search_results, collection, product_detail, cart, and checkout. Every dispatch tells your agent which screen it landed on, so state is never a guess: search_products puts you on search_results (where filter_results, sort_results, and view_product operate), view_product lands on product_detail (home of select_variant, add_to_cart, and view_reviews), browse_category reaches collection, cart actions resolve on cart, and checkout moves the session onto the checkout screen. Your agent plans against these screen states rather than parsing pages.