Amazon for AI Agents

The amazon.com config covers four jobs.

**Finding products.** search_products navigates straight to the results URL (the fast path, a direct link instead of typing into the search box), search_in_department scopes a query to one storefront, and view_search_suggestions reads Amazon's live autocomplete without leaving the current screen. Beyond keyword search there are the charts (view_best_sellers and view_new_releases, both refreshed hourly, plus most-gifted and most-wished-for), the Today's Deals and Lightning Deals grids, the coupons collection, and category browsing by Amazon's own node ids.

**Researching one product.** open_product jumps to a product page by its 10-character ASIN, and open_url accepts any pasted Amazon link, including a.co and amzn.to short links. From the product page your agent reads the About-this-item bullets and spec table, the delivery estimate by the buy box, reviews (filter_reviews handles star, verified-purchase, keyword, sort, and page facets), and the full third-party offer list via view_buying_options or view_used_and_new for condition-filtered offers. view_seller_page resolves a storefront to the legal registered business name and address behind it, which is frequently not the display name.

**Cart.** Add from the product page or inline from search results, set and step quantities, remove lines, and move items between the cart and the Save for later list.

**Account, signed in.** Order history with keyword, time-window, and status filtering, per-order detail and invoices, package tracking, returns status, Subscribe & Save subscriptions, Prime status, gift card balance, digital content, and read-only views of saved addresses and payment methods (card type and last-4 only, never full numbers).

These come straight from the mapped config, not from guesswork.

• **Step-up auth on account screens.** Amazon demands recent authentication for orders, tracking, invoices, returns, and the other account reads. A stored session goes stale within about an hour and bounces to the sign-in wall even with valid cookies. On a bounce, re-run the Connect sign-in; retrying the action does nothing.
• **Checkout stops at the sign-in boundary.** Amazon has no guest checkout, so checkout always routes to the sign-in screen and never places an order. The mapped surface builds and manages the cart; it does not buy.
• **Sort and page carefully.** sort_results and paginate_results rebuild the search from the bare query and drop applied filters. To keep filters, page with next_page/prev_page (they click the live pagination links) and sort with sort_results_in_context. To stack facets, read the live facet list with read_available_filters and navigate each option's apply_url via apply_filter: Amazon merges facets into one URL fragment that only its own discovered hrefs reflect.
• **The cart quantity control is a stepper, not a dropdown.** update_quantity moves one step per call, and at quantity 1 the decrement control is the Delete button, so stepping down removes the line. Re-read the cart after each change. Variant picks work the same defensive way: select_variant attempts the selection, and your agent re-reads the product page to confirm it took effect.

Most of the surface is public: 61 of the 79 actions run anonymously, including everything in search, browse, deals, product detail, offer listings, seller pages, and the cart. Your agent can even set a delivery ZIP anonymously with set_delivery_location so prices, stock, and delivery estimates reflect a real location.

The 18 signed-in actions are the account reads plus save_to_wishlist, which needs an account to persist (Amazon redirects an anonymous Add to List click to the sign-in wall).

The config carries a full auth block: Amazon's real /ap/signin login URL, the session cookies that prove a login (session-id, ubid-main, x-main, at-main), and the page indicators that detect a sign-in bounce. Sign-in itself is scripted as Amazon's actual two-step flow: sign_in_email submits the email or mobile number and continues, then sign_in_password completes authentication. Keep the step-up rule in mind: account screens want recent auth, so plan to re-run sign-in during long sessions.

Results come back as structured records per screen, so your agent never parses markup.

• **search_results** returns listing records plus the total result count, and read_available_filters returns each live facet option as {option_label, apply_url, result_count}, ready to feed back into apply_filter.
• **deals** serves both the Today's Deals and Lightning Deals grids as deal cards with title, price, discount, and deal badge.
• **coupons** returns coupon cards: coupon_title, coupon_url (the product page), coupon_price (what you pay with the coupon), and a best-effort percent-off discount.
• **product_detail** records include the buy-box seller_id, which feeds view_seller_page directly.
• **seller_page** returns the seller's legal name and business address plus display name, feedback star rating, and trailing-12-month percent positive and rating count.
• The signed-in screens (**order_history**, **order_detail**, **order_tracker**, **returns_center**, **subscriptions**, and the rest) return account data the same way. One useful detail: view_orders hands back an order_detail_url per order, and passing it as detail_url to open_order_detail_url covers order types the generic detail form does not, such as Whole Foods orders.