JCPenney for AI Agents

The config covers the whole shopping loop. For discovery, search_products types a query into the header search box and works from any screen where the header is visible, and open_department opens one of nine top-level departments (women, men, juniors, baby-kids, home-store, shoes, jewelry-and-watches, beauty-and-salon, sale). On listing pages, apply_filter narrows by whatever filter groups the category exposes (color, size, brand, price range, and so on), sort_results switches between six sort orders from 'best match' to 'price high - low', and go_to_page pages through results.

On a product page your agent picks a variant with select_size and select_color, sets a quantity with set_quantity, and calls add_to_cart. Success is confirmed by the mini-cart side panel opening and the header bag counter incrementing; the site shows no toast and does not navigate. open_reviews expands the Bazaarvoice reviews region and view_size_guide opens the department-specific size guide.

In the cart, update_quantity, remove_from_cart (immediate, no confirmation dialog), save_for_later, and apply_best_coupon (applies the Best Coupon banner at the top of the cart, raising Total Savings by the advertised amount) manage the bag. Checkout runs through the sign-in/guest gate onto the shipping step: continue_as_guest, enter_shipping_address, set_delivery_mode to toggle Ship to Home vs Ship to Store, then continue_to_payment. After purchase, track_order looks up any order by order number plus phone on the public tracking page, and find_stores_near finds stores by zip, city, or city plus state.

These come straight from the mapped action behavior, and Rindler already compensates for each one.

**Size buttons toggle.** Re-clicking an already-selected size deselects it. select_size only clicks when the target size is not already active, so your agent never accidentally unpicks a variant.

**The main nav is hover megamenus, not links.** open_department skips the hover dance and navigates directly to the department URL. Pagination has the same problem: numbered page indicators render as generic divs, not links, so go_to_page rewrites the page parameter in the URL instead of clicking.

**The cart has two identical Checkout buttons** (a primary one and a sticky mobile one). checkout targets the first match inside the Order Summary region so the duplicate is never the one clicked.

**Filter values are case-sensitive and stock caps are real.** apply_filter values must match the on-screen label exactly ('Blush', not 'blush'; 'under $5' for price buckets), and the quantity comboboxes on both the product page and the cart are stock-capped, so a 'Hurry, 2 left!' item tops out at 2.

Most of the surface is public. Search, browsing, product pages, the cart, order tracking, and the store locator all work with no account. Only four actions require auth in the config: checkout, save_for_later, save_to_wishlist, and view_order_detail.

The gate itself lives at jcpenney.com/cart/signin, and open_sign_in reaches it by direct URL because the header account dropdown has no accessible label. From there your agent has two lanes:

**Guest.** continue_as_guest proceeds without an account and lands directly on the shipping step of checkout. For a straight purchase this is the shortest path.

**Account.** The login action takes email and password params and fills the form itself; credentials are redacted from logs and responses. It proves success by navigating to the authed account dashboard, where an unauthenticated hit redirects back to the sign-in page. That means a wrong password or an OTP step reports as a real failure instead of a false 'you're logged in'.

Nine screens are mapped: homepage, department_landing, plp, pdp, cart, cart_signin, checkout_shipping, order_tracking, and store_locator.

A typical session starts on homepage, reaches plp via search or department_landing via open_department, drills into a pdp with view_product, builds the bag on cart, passes the cart_signin gate, and finishes on checkout_shipping, where address, delivery mode, and the advance to payment happen. order_tracking and store_locator stand alone and are fully public, so a track-my-order or find-a-store task never touches the purchase flow at all.

Every dispatch reports which screen the session landed on and which actions are valid there, so your agent always knows where it is without parsing the page.