Meta Muse for retailers: how Meta's shopping agent reaches your store and what to do

Direct answer: Muse is Meta's personal AI agent. It reaches a retailer in three ways: through Shopify Catalog and direct checkout on Meta, through a connector the retailer (or its platform) has built and Meta has approved, or through its own browser, which fills in your normal checkout and pays with Link by Stripe. Only the first two are routes you opt into. The browser route needs nothing from you, and Meta publishes no user agent for it, so robots.txt does not control it. Amazon has blocked Muse. Many retailers will decide differently, and should then make sure their checkout works for it.

This guide is for ecommerce directors, heads of digital and engineering leads. It sets out what Muse is and where it runs, what each route means for your store, what the Amazon dispute does and does not tell you, what we found in the robots.txt files of the 225 retailers in our Agent Commerce Index, and what to check first.

Last verified: 27 October 2026 against Meta's announcements, Help Center and research blog, the Muse Connector Platform guidelines, Shopify's Help Center, Stripe's announcement and Meta's crawler documentation. Muse is new and changes often, so check the current versions before you plan work.

What Muse is and where it runs

Meta launched Muse on 8 September 2026 as an agent that plans and completes tasks rather than only answering questions. The points that matter to a retailer:

• It runs in the cloud, not on the shopper's phone. Muse works on a per-user virtual machine Meta calls the Muse Secure VM, with its own browser. Meta says it can "open a browser, fill out forms" and keep working after the user closes the app.
• It asks before it buys. Meta says Muse checks with the user before sensitive actions such as making a purchase. Its research blog says Muse detects checkout pages and asks for human approval each time.
• It does not see the card. Meta says Muse "has no visibility into people's passwords or payment methods". Credentials go into a secure store Muse can use without reading.
• It pays with Link. Muse checks out with Link by Stripe. Meta's launch post says Shop Pay is coming soon, and at Connect on 24 September Meta said it was adding Shop Pay and PayPal.
• Where it is available. Meta's Japan launch post of 23 October 2026 calls Japan the first market outside North America, where Muse launched in September. Meta's Help Center says Muse is "not yet available everywhere". We found no announcement for the UK or EU. Many features are free, with paid subscription plans.

The shopper's location matters more than yours. A UK store that ships to the US can already receive Muse sessions from US users.

Three ways Muse reaches a store

Route 1: Shopify Catalog and direct checkout on Meta

At Connect on 24 September Meta said Muse had launched with access to the entire Shopify catalogue. Shopify's Selling on Meta page explains what that means for a merchant.

• It is on by default. Direct checkout on Meta surfaces, including Muse "when available", is on by default for eligible stores.
• Eligibility. You must sell to the US, Canada, Mexico, Brazil, Japan or Singapore, have Catalog-eligible products, agree to Shopify's Agentic Storefronts Supplemental Terms and have terms of service, privacy and return or refund policies in place. Direct checkout is shown only to customers in those six countries.
• What it excludes. Products that need checkout blocks, subscriptions, bundles, customisable products, B2B-only products, local delivery or pickup, or sign-in are not supported. Shopify Functions and discounts are.
• Fallback. If Meta cannot collect what the order needs, the shopper is sent to your own checkout in Meta's in-app browser with the cart preserved.
• Money and liability. Orders are attributed to Meta and you remain merchant of record. Shopify says there are no fees beyond payment processing.
• Measurement. Google Analytics and custom pixels do not fire. Only server-to-server pixel events for checkout started and completed are sent.
• Product copy. Shopify asks for legal disclosures to sit within the first 6,000 characters of a product description.

To change it, go to Sales channels > Agentic, turn off Allow Shopify to manage for me, open Meta AI and Muse, and set Shopify Catalog access and Direct checkout separately. Shopify notes that with catalog access off, your products might still be shown through other methods such as web crawling and indexing. With direct checkout off, shoppers are sent to your online store to buy.

Separately, Shopify offers a Shopify connector for Muse for merchants. It lets you manage products, inventory, orders, discounts and analytics from Muse. It is an admin tool, not a sales channel.

Route 2: connectors

Connectors let Muse act through a service's API instead of its website. At Connect, Meta said it was adding retailers including Walmart, Best Buy, American Eagle Outfitters, DICK'S Sporting Goods, Fanatics, Gap, Michael Kors, Sephora, Ulta and Wayfair. Businesses can apply through the Muse Connector Platform. The guidelines set a high bar:

• Finish the task. If your service supports purchasing, the connector should handle search, pricing and terms, checkout and confirmation, plus status checks, returns and refunds where you offer them. It should support guest checkout. Sending the user to finish the whole checkout elsewhere "does not meet the completion requirement".
• Beat the browser. Meta says Muse "can already browse websites", so a connector must add something, such as account access, more reliable actions or fewer steps. "A wrapper around public pages or a list of links alone is not enough."
• Approval every time for purchases. Purchases count as sensitive writes. The user approves each one and cannot set them to "Always allow".
• Full prices before commitment. Tools must return the seller, full price and currency, recurring charges, key terms and the cancellation or refund policy before the user commits.
• Review. Submissions need business verification, a data-processing questionnaire, credentials and a test account. Meta reviews them for risk, tool by tool and end to end, and featuring is a separate editorial decision.

For most mid-market retailers, a connector is a later project. If your platform already gives Muse your catalogue and checkout, as Shopify does, the platform route comes first.

Route 3: Muse's own browser

Here is what Meta says about the browser.

• What it is. Meta's research blog describes a real, up-to-date Chromium-based browser running behind virtualisation. The browser sub-agent works from an accessibility tree snapshot rather than the raw DOM, and does not run JavaScript in the page context. Your site's own scripts still run in a real browser; Muse reads the result through the accessibility tree.
• It acts as the user. The research blog says that when Muse browses, "it will appear as your activity": a site the user's Muse visits may treat it as the user's visit, for example for advertising. Meta's Help Center page on how Muse browses the web says the user can take control or stop it at any time, and that it may accept essential cookies on third-party sites.
• No documented user agent. Meta's web crawlers page, last updated 21 May 2026, does not mention Muse. The closest entry is Meta-ExternalFetcher, which "fetches individual links at a user's request" and supports "helping AI navigate websites to complete tasks for users", so it "may bypass robots.txt rules". Cloudflare Radar lists Muse as an agent operated by Meta with "intermediary" access and "[no user agent provided]".
• How it pays. Stripe says that at more than a million businesses that accept Link, Muse checks out with the US user's saved payment method. At other businesses, "Link issues Muse a single-use virtual card scoped to the approved purchase." Meta's research blog adds that the card is tied to the merchant and amount and lasts a limited time.

What this means for your checkout:

1. Your normal checkout is the agent's checkout. Anything that stops a careful new customer stops Muse: forced account creation, a card form in an iframe that does not load, a price that changes at the last step.
2. Bot defences meet a cloud browser. Muse runs in the cloud, and Meta documents no way to identify it. A rule that challenges data-centre traffic or automation signals on cart or checkout can block it, even if you never meant to. Our guide to page-fetching and browsing agents explains why browsing agents fail where fetchers pass.
3. Card risk rules meet virtual cards. A single-use virtual card for the exact order total is how the browser route pays at stores that do not accept Link. Check that your fraud rules do not decline single-use or virtual cards by default.
4. A total that changes after approval fails. Each payment is approved for an amount. Shipping or fees that appear only at the final step can push the total past what the user approved.

The Amazon dispute: what it does and does not tell you

On 20 September 2026 Amazon started showing Muse users a popup: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, to which our customers have agreed." GeekWire reported Amazon's reasons: Meta did not tell Amazon that Muse would access its store, the agent does not identify itself when it browses, and it appears to capture and store customer credentials. An Amazon spokesperson said third-party applications "should operate openly and respect service provider decisions about whether or not to participate". Meta has said Muse has no visibility into passwords or payment methods. GeekWire also notes that Amazon earns advertising revenue from people browsing its pages.

Two lessons for other retailers:

• Blocking Muse is a bot-management decision, not a robots.txt line. Amazon relied on its own detection and its Conditions of Use. With no published user agent, you cannot single Muse out with a simple rule. Blanket rules against cloud browsers will also catch other agents you may want.
• Amazon is a marketplace and ad business. Most retailers are not. For a store that wants sales, an agent that arrives with a purchase intent and a scoped payment is a customer. The more useful question is whether your checkout lets it finish. Our guide to whether you are blocking AI shopping agents covers the full decision across robots.txt, CDN and WAF.

What we found in the Index

On 27 October 2026 we fetched robots.txt for the 225 scored retailers in the Agent Commerce Index and got a readable file from 209.

Two points stand out. Few retailers have written any Meta-specific rule, and the most common one names Meta-ExternalAgent, which Meta describes as its crawler for training AI models and indexing content, not a shopping agent. None of them could govern Muse's browser in any case, because Meta publishes no token for it. The control that matters is bot management on cart and checkout, which robots.txt cannot show.

129 of the 225 scored Index retailers run on Shopify. Muse's Shopify Catalog route can reach them if they meet the eligibility rules above. We did not check which ones have direct checkout on Meta turned on, because that setting is not public.

What to do this week

1. Decide your position on Muse on purpose. Write down whether you want Muse sessions to buy. If yes, the work is on checkout and bot rules. If no, accept that blocking it needs bot management that can also catch other agents.
2. If you are on Shopify, check Sales channels > Agentic. Confirm whether Shopify Catalog access and Direct checkout for Meta AI and Muse are on, whether your products are eligible, and whether your policies are complete. Agree how Meta-attributed orders will be reported, since GA and custom pixels do not fire.
3. Test checkout from a cloud browser. Run your purchase journey as a guest from a data-centre IP in a standard Chrome browser. Look for challenges on cart and checkout, forced sign-in, card iframes that fail to load and late price changes. TRX-01 (guest checkout), TRX-02 (cart reachable by agent identities) and TRX-03 (no captcha on cart or checkout) in our specification cover the same ground.
4. Ask your payments team about virtual cards. Confirm that single-use virtual cards are not declined by default, and whether you accept Link.
5. Show the full price early. Put shipping, delivery time and returns on the product page and in structured data, so the total the user approves matches the total at checkout.
6. Review connectors later. If you have an API that does something the browser cannot, such as accounts, loyalty or live stock, read the Muse Connector Platform guidelines before you commit to building one.

To watch where a browsing agent drops out of your cart and checkout, the Simulated Agent Buyer runs browser agents through your purchase flow and records each step. Our overview of agentic commerce for retailers puts Muse alongside ChatGPT, Google's Universal Cart and the rest.

Sources

• Meta, Introducing Muse: The World's First Personal AI Agent Built for Everyone, 8 September 2026, updated 30 September 2026
• Meta, The Biggest News From Connect 2026, 24 September 2026
• Meta, Muse launches in Japan (Japanese), 23 October 2026
• Meta AI Research, How We Built Safety Into Muse, 8 September 2026
• Meta Help Center, How your Muse agent browses the web and Muse Help Center, read 27 October 2026
• Meta, Muse Connector Platform: connector guidelines, read 27 October 2026
• Meta for Developers, Meta Web Crawlers, updated 21 May 2026
• Shopify Help Center, Selling on Meta and Shopify connector for Muse, read 27 October 2026
• Stripe, Stripe helps Muse, Meta's new personal AI agent, shop across the internet with Link, 8 September 2026
• Cloudflare Radar, Muse bot information, read 27 October 2026
• GeekWire, Amazon blocks Meta's Muse AI assistant in new standoff over agentic shopping, 20 September 2026, updated 22 September 2026
• ConversionVector, robots.txt fetch of the 225 scored Index retailers, 27 October 2026; Agent Commerce Index Q4 2026 (CC BY 4.0) and Agent Conversion Score specification v0.6