AI shopping agents: compare the checkout, not the hype.
Seven agents. Different checkouts. Compare payment, approval and retailer responsibility before deciding what to support.
Short answer: there is no single best shopping agent for every retailer. Copilot Checkout documents an in-chat merchant route; Muse supports both Link and saved merchant cards; dots documents saved-card purchases; Instinct and Grok Bot have confirmed Link support. Spark works through connected apps, while Cue's wallet mechanics remain unclear. Do not treat these as seven identical shopping services.
Documentation checked 9 October 2026. No agents were tested, no purchases made, and no conversion or reliability ranking is claimed. Unknown does not mean unavailable or free.
Product or vendor marks identify the entries; they do not imply endorsement. OpenAI, Gemini, Manus and xAI marks represent their product families where a separate agent mark was not established.
Seven agents, four questions retailers should ask
| Agent / type | Purchase route | Approval and retailer responsibility | Access, cost and limits |
|---|---|---|---|
Personal buyer | Link or a saved merchant cardRead detailLink checkout, or merchant login with a saved card. Link can use a wallet payment at participating businesses or a purchase-scoped virtual card elsewhere. | Approval before every purchaseRead detailMeta says approval before every purchase. Merchant fulfils the order; supported location, merchant and checkout matter. | US Link documented; wider access varies |
Personal buyer | Link agent paymentsRead detailStripe lists Instinct as supporting Link agent payments. Link documents purchase-scoped credentials; this is not proof of a special retailer feed or universal checkout access. | Approve the amount in LinkRead detailLink documents amount approval before purchases. Instinct terms place the purchase and merchant terms with the customer, not Instinct as seller. | Markets and merchant commissions not verified |
Personal / work assistant | Card saved on merchant siteRead detailCan buy using a card already saved on the merchant website. A logged-in browser session is documented; not the same product as ChatGPT Instant Checkout. | Approval, including specifically scoped advance approvalRead detailPurchase approval is required, but may be given in advance when it specifically covers that purchase. Money transfers require takeover. | Retailer account and saved card neededDetail and sourcesMerchant account/card needed for this route. Standalone price, complete markets and a retailer integration programme not verified. Source Last verified: 9 October 2026 |
Personal agent | Partner apps, including InstacartRead detailGoogle documents connected apps including Instacart for groceries. A partner-app action is not evidence of open checkout on every retailer site. | Designed to ask before spendingRead detailGoogle says it is designed to ask before high-stakes actions such as spending. Current help warns scheduled tasks can make unintended actions and may need supervision. | Pro/Ultra; unavailable in UK and other listed markets |
Personal team of agents | Agent has its own walletRead detailManus documents separate agent identities, including a wallet, email, phone and computer. It does not specify the wallet payment rail in the source checked. | Spend limits and approval rules unknownRead detailWallet spending caps and purchase-approval mechanics not verified. A statement that the user makes the final call is not a documented per-purchase control. | Invitation code; payment rail and price unknownDetail and sourcesInvitation code required. Cue-specific price, merchant charges and supported checkout/account-matching route unknown. Source Last verified: 9 October 2026 |
General-purpose agent | Link agent paymentsRead detailStripe and Link confirm agent-payment support for Grok Bot. Link provides approved spending credentials; xAI documents a persistent computer and connected work tools. | Approve the amount in LinkRead detailLink says the user approves the amount before purchases. Do not assume planned autonomous budget controls are available in this integration. | Shopping markets and merchant fees not verified |
In-chat checkout, not a delegated personal buyer | Embedded checkout inside CopilotRead detailSupported products can be bought inside Copilot. Stripe documents ACP and a Shared Payment Token passed to the seller after buyer payment details are provided. | Buyer completes checkout; retailer is merchant of recordRead detailThe buyer completes the checkout. Microsoft and Stripe say the retailer remains merchant of record and controls the customer relationship/data. | US rollout; retailer onboarding routes documented |
What changes at the checkout?
Link support does not mean every order uses a new card
Stripe describes two Muse routes: an existing Link payment method at businesses that accept Link, and a single-use virtual card scoped to an approved purchase elsewhere. Meta also documents purchases with a card saved in the merchant account. A blanket claim that every Muse order uses a new virtual card would be wrong. Stripe payment detail; Meta payment help.
Link lists Muse, Instinct and Grok Bot as supporting agent payments. Its feature matrix does not mark those three as supporting Link financial insights, even though Stripe now offers that capability to agent builders. Do not turn a platform announcement into a live feature claim for every agent. Current supported-feature matrix; Stripe update.
Saved-card purchases are different from embedded commerce
Dots can use a card saved on a merchant website, with approval that can be scoped in advance. Copilot Checkout instead embeds checkout in the chat for supported products. Stripe sends a Shared Payment Token to the seller, who remains merchant of record. Neither fact guarantees account matching, loyalty points or returns reconciliation in your own store. Test those separately. Dots approval rules; Copilot payment flow.
A wallet is not a published spending policy
Cue has an agent wallet according to Manus. We did not establish its payment provider, spend caps or per-purchase approval rules. The Google Spark announcement describes asking before spending, but a general AP2 protocol announcement would not prove that every Spark partner checkout uses that protocol. Those gaps stay visible rather than being filled from a competitor table. Cue documentation; Spark announcement.
Shopify WebMCP is a checkout interface, not universal permission
Shopify documents browser tools to read and update an active checkout and submit it after buyer confirmation. The buyer handles interactions such as Shop Pay login, 3D Secure or blocking extensions. The tools use the checkout UI state and do not require merchant configuration. This supports a browser-agent journey, not a promise that every agent or every checkout works. Checkout WebMCP docs.
Shopify calls these eligible checkouts. If checkout tools are not available, its storefront docs tell the agent to hand the buyer over to the page. Browser WebMCP also differs from server-side Checkout MCP. Do not assume support for one means support for the other, or that this table proves any named agent has integrated them. Storefront tool limits.
A retailer's acceptance checklist
These are practical checks to run in your own systems, not claims that the agents above already pass them.
- Product truth: keep variant size, compatibility, stock, full price, delivery dates and return terms consistent across product pages and feeds. A lifestyle description cannot substitute for the exact item being ordered.
- Identity and loyalty: check whether an approved order enters as a recognised account or guest. A token or new card number alone does not tell you whether the shopper is new.
- Payment and fraud: inspect authorisation, billing/contact fields, payment challenges and duplicate-order handling. Preserve the same fraud controls you use for people.
- Customer responsibility: make confirmation, cancellation, refunds, delivery exceptions and support discoverable. Do not equate an assistant's approval screen with your own return policy.
- Merchant controls: verify actual onboarding, opt-out settings, catalogue inclusion and fees in your provider account. A launch announcement is not your current contract.
- Safe actions: validate price, stock, buyer approval and allowed actions in your backend. Product descriptions and reviews are data, not instructions to the assistant.
- Measurement: distinguish observable agent-assisted sessions from guessed bot traffic. Keep a record of the payment route and order outcome; do not claim agent conversion uplift from downloads.
Common questions from retailers
Can an AI agent check out on a retailer's site?
Several documented routes exist. Link lists Muse, Instinct and Grok Bot as supporting agent payments through Link checkout. Meta documents purchases with a card saved in the merchant account. Copilot Checkout embeds checkout in the chat for supported products, with Stripe sending a Shared Payment Token to the seller. Shopify documents browser tools that read and update an active checkout and submit it after buyer confirmation. Documentation checked 9 October 2026; no hands-on purchase tests.
Who is the merchant of record when an AI agent pays?
On the Copilot Checkout route, Stripe sends a Shared Payment Token to the seller, who remains merchant of record. On the other documented routes the merchant fulfils the order. Approval, fraud checks and fulfilment terms differ per route, so confirm them in your own payment stack rather than assuming one model fits all seven agents.
Does Link support mean every agent order uses a new card?
No. Stripe describes two Muse routes: an existing Link payment method at businesses that accept Link, and a single-use virtual card scoped to an approved purchase elsewhere. Meta also documents purchases with a card saved in the merchant account. A blanket claim that every order uses a new virtual card would be wrong.
Do agent orders preserve accounts, loyalty and returns?
Not by default on the documented routes. Neither saved-card purchases nor embedded in-chat commerce guarantees account matching, loyalty points or returns reconciliation in your own store. Test those separately before treating agent orders like returning-customer orders.
What should a retailer check before supporting agent checkouts?
The acceptance checklist above spells out seven areas: product truth (variants, stock, price, delivery and return terms consistent across product pages and feeds), identity and loyalty (recognised account or guest), payment and fraud (unchanged fraud controls, duplicate-order handling), customer responsibility, merchant controls (onboarding, opt-out settings, fees in your provider account), safe backend actions, and measurement that separates observable agent sessions from guessed bot traffic. These are checks to run in your own systems, not claims that the agents already pass them.
What this comparison deliberately leaves out
We do not repeat unverified transaction-volume, valuation, market-share or partnership claims. We do not rank agents by purchase success, refund handling or retailer friendliness without comparable tests. Retailer-specific fees and contracts are not a universal price list. Where an official source describes a rollout rather than current global availability, the table says so.
Copilot Checkout is not Copilot Studio or Microsoft work agents. Dots is not ChatGPT Instant Checkout. Cue is not every feature in the general Manus product. Spark is not interchangeable with every Google Shopping checkout. This page keeps the seven entries from the original idea without merging different products.
How this page stays current
Each row has a last-verified date and primary-source links. We include this page in the regular site research cycle: check changed payment, access and approval documentation, then update affected rows after the evidence and visual gates pass. A full comparison review belongs in the fortnightly research audit. We do not refresh dates without rereading the relevant sources.
Announcements are evidence of what a company said on that date, not proof of rollout to every merchant. If sources conflict or stop answering a question, the row gets an explicit gap rather than an inferred answer. See our methodology and corrections policy.
Sources and further reading
The retailer-facing angle was suggested by Roger Dunn's 5 October comparison. Its prose, ratings and image table are not reproduced. All product facts above were checked against the linked company or payment-provider sources.
- Meta
- Muse Stripe
- Link
- Wallet
- Link Update
- Instinct
- Dots
- Spark
- Spark Apps
- Spark Intro
- Cue
- Grok
- Copilot
- Copilot Stripe
- Shopify
- Shopify Store
Related: Personal assistant agents, Privacy and approval checklist, Muse, Instinct, Dots, Cue.