Handing an AI shopping agent's cart to your Magento checkout
Agent Checkout Handoff is a free extension that gives an AI shopping agent a single-use link: the shopper opens it and lands in Magento checkout with the cart the agent built, and the agent's cart ID stops working.
ExtensionA shopper tells a chat assistant what they need, and the assistant finds it, picks the size and puts it in a cart. Then comes the step where the shopper has to pay, in their own browser – and on most stores built on Adobe Commerce and Magento Open Source that step lands on an empty cart.
What it is for
Agents build carts through Magento's GraphQL API, and those carts belong to no browser. The checkout shows only the cart of the browser's own session, and the platform has no storefront address that opens checkout for a given cart. The obvious workaround – put the cart ID in a link – hands out a key to the cart: the masked cart ID is a bearer credential, and whoever holds it can keep changing items and addresses while the shopper is paying.
Agent Checkout Handoff is an extension for Magento Open Source and Adobe Commerce that turns that last step into one link. The agent's backend calls a GraphQL mutation with the cart ID and gets back a link that works once and expires in minutes. The shopper opens it and lands in checkout with the agent's cart, on Luma or Hyvä Theme. At that moment a guest cart gets a new cart ID: the one the agent held stops working, so the cart is the shopper's alone.
Nothing about the checkout itself changes. The shopper pays in the store's own checkout, with the store's own payment methods, shipping rules and prices. The extension is deterministic, runs entirely in the store and calls nothing outside it.
How it can be used
A chat assistant on your own store. Your assistant answers product questions and builds carts as a guest. When the shopper is ready, the assistant asks for a link and shows it in the chat. This is the simplest case: guest cart, guest browser, straight to checkout. If the shopper already had a cart of their own in that browser, a setting per store view decides whether the agent's cart replaces it or is merged into it.
An agent platform that shops for its users. A third-party agent connects to your store's GraphQL API and builds the cart on its side. It sends your link to its user; the link opens on your storefront, on the store view the agent called, in that store's language and currency. The agent never needs to know whether the shopper is signed in on your site – a signed-in shopper gets the items merged into their account cart, as at any sign-in.
Stores that require an account. With guest checkout switched off, the link takes the shopper to the sign-in page with a notice that the cart is ready; after signing in they land in checkout with the agent's items. A cart the agent built for a customer, with that customer's token, opens for that customer only: anyone else is refused, and the link stays valid for its owner.
In every case a link that is expired, used or opened on the wrong store view ends on the cart page with one generic message. The agent issues a new one.
How it compares
A store has four ways to get an agent's cart to the shopper. They differ in who can use them and in what they expose.
| Approach | Guest shoppers | Exposes the cart ID | Works on any browser state |
|---|---|---|---|
| A plain link to the checkout | No – the cart is empty | No | – |
| The agent writes to the customer's account cart; the shopper signs in | No – customers only | No | Only after sign-in |
| A link carrying the cart ID (or a signed copy of it) | Yes | Yes – a reusable key to the cart | Depends on the module |
| Agent Checkout Handoff | Yes | No – a single-use token; the cart gets a new ID on open | Yes – guest, signed in, own cart, guest checkout off |
The account-cart route is the one Magento supports out of the box, and for an agent that only serves signed-in customers it is enough – no extension needed. It does nothing for the guest shopper, who is most of an agent's traffic.
A link with the cart ID in it does reach guests, and many share-cart and cart-restore features work that way. Signing the ID does not help here: the link still carries a credential that keeps working after the shopper opens it, and anyone who saw the link – in a chat log, a browser history, a shared screen – can go on changing the cart. The handoff link carries a random token instead, stores only its hash, works once, expires within an hour at most, and the cart it opens gets a new ID.
What the alternatives do better: the account-cart route needs no installation at all, and a cart-ID link survives being opened twice, which some flows want. If every shopper your agent serves is signed in, start there.
What it does not try to be
It does not build carts, search the catalog or talk to any agent platform – the agent does that over Magento's own GraphQL API. It is not a checkout, a payment method or a headless storefront. The FAQ lists what is out of scope and when a different tool is the better choice. Any agent backend that builds its cart over Magento's GraphQL API can hand it over through this extension.