Meta opened its Muse Connector Platform to outside developers on Sept. 18, letting anyone plug a product into Muse -- the personal AI agent Meta launched Sept. 8 under chief AI officer Alexandr Wang -- and, separately, partnered with Stripe so Muse can check out using Stripe Link, the same payment rail it already uses for its own transactions. Notion and Granola went live as the first new connectors, giving Muse access to a user's documents and meeting notes respectively, on top of the existing set Wang had named in an earlier post: Gmail, Google Calendar, Outlook, Plaid, OpenTable, Spotify and others. "We're opening muse connectors to developers," Wang wrote, adding that Meta had "seen so much excitement in the developer community, integrating muse into everything from robots to mood lights." The same evening, Muse expanded to Canada with Link-wallet purchase support.
The platform draws a real line between two kinds of connector: directory connectors, which Meta reviews before listing them in Muse's settings, and custom connectors, which Muse can write on the fly for one user and which nobody else vets. Getting into the directory means describing the product, passing Meta's review for "functional, security, legal requirements" plus end-to-end testing, and, for the ones Meta picks, editorial placement in the directory. What muse.ai/platform does not publish is any fee schedule, revenue share, or developer terms -- a business deciding whether to build a connector is doing so without knowing what Meta will eventually charge for the placement.
From a submitted API to a completed purchase
- Describes the product and submits it through muse.ai/platform.
- Reviews for functional, security and legal requirements, plus end-to-end testing.
- Lists the connector in the user-facing directory, with optional editorial featuring.
- Pays through Stripe Link using credentials Meta says sit in encrypted storage Muse can use but not see.
Amazon didn't wait to find out how that would play out on its own site. By Sunday evening -- 12 days after Muse's launch -- Amazon began showing anyone completing a purchase through Muse a popup reading: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, to which our customers have agreed." An Amazon spokesperson said the company had asked Meta beforehand to keep Amazon out of Muse's scope, and framed the block around three specific complaints: Meta gave no advance notice of the agent's activity, Muse doesn't identify itself as an AI agent when it browses, and it captures user credentials. "We think it's fairly straightforward that third-party applications that offer to make purchases on behalf of customers from other businesses should operate openly and respect service provider decisions about whether or not to participate," the spokesperson said. Meta disputed the credentials point directly: Muse "has no visibility into people's passwords or payment methods," a spokesperson said, because they "go into secure storage, so Muse can use them without seeing them." Neither company's claim about what Muse can actually see has been independently tested.
“We think it's fairly straightforward that third-party applications that offer to make purchases on behalf of customers from other businesses should operate openly and respect service provider decisions about whether or not to participate.” — an Amazon spokesperson, quoted by Forkast News
Amazon can block Muse with more legal confidence than it had six weeks earlier, when it tried the same fight against Perplexity's Comet browser and lost. In Amazon.com Services v. Perplexity AI, decided Aug. 4, the Ninth Circuit vacated Amazon's injunction against Perplexity's shopping agent, holding that it was the user, not Perplexity, who "accessed" Amazon's computers under the Computer Fraud and Abuse Act -- because Comet runs locally on the user's own machine, taking screenshots of what the user's browser shows and sending instructions back, without Perplexity's own servers ever talking to Amazon's directly. Muse works the opposite way: it runs on Meta's own cloud-hosted browser and holds the user's stored login. That's exactly the distinction the Ninth Circuit said it was leaving open -- the court noted that an agent exercising "greater control," where "the company's servers communicated directly with the defendant's servers," could support a different outcome. (The ruling also explicitly preserved Amazon's ability to bring contract and tort claims -- including breach of its terms of service -- regardless of how the CFAA question comes out. That door stays open whether or not Amazon ever walks through it against Meta.)
How agentic shopping got its first tollgate
- Aug 4, 2026 — Ninth Circuit vacates Amazon's CFAA injunction against Perplexity's locally-run Comet browser -- but explicitly leaves cloud-hosted agents and contract claims unresolved.
- Sept 8, 2026 — Meta launches Muse; Wang names its first batch of connectors, including Amazon-adjacent services like Plaid and OpenTable.
- Sept 18, 2026 — Meta opens the Muse Connector Platform to outside developers, adds Stripe Link payments, and expands Muse to Canada.
- Sept 20, 2026 (Sun.) — Amazon begins blocking Muse checkouts with a Conditions-of-Use popup.
The stakes for each company are different shapes of the same bet. Meta is trying to turn Muse from a chat interface into a transaction layer -- the Connector Platform and the Stripe deal only matter if agents actually get to complete purchases on other companies' sites, not just Meta's own. Amazon's storefront is the single biggest test of whether any outside agent can do that without the retailer's permission, and it has now said no twice in six weeks, first in court and now at checkout. Stripe, notably, is exposed to neither side's dispute -- it gets paid whether the purchase completes on Amazon or on a merchant that welcomes Muse instead.
- Its biggest connector ambitions depend on retailers' cooperation, and its largest one just said no at checkout.
- Sets a public precedent -- block first, litigate later if needed -- that other retailers can copy without going to court.
- Gets paid on a Muse purchase regardless of which merchant it completes on, Amazon or otherwise.
- Have no published fee or revenue-share terms from Meta, and no independent read on whether Muse's credential handling is as safe as Meta says.
Nothing here is settled. Amazon's block is enforced by a popup, not a court order, and the Ninth Circuit left it an actual path to one if it wants -- the contract and tort claims the CFAA ruling never touched. Meta's credential-storage defense hasn't faced outside scrutiny. And the one company positioned to win regardless of who's right, Stripe, isn't a party to the fight at all.
- Meta opened Muse Connectors to outside developers Sept. 18, plus Stripe Link payments and a Canada launch.
- Notion and Granola went live as connectors; Meta reviews submissions for function, security and legal issues.
- Amazon blocked Muse from checkout Sunday evening, saying it captures credentials and doesn't identify itself.
- Meta says Muse never sees passwords -- credentials sit in encrypted storage it can use but not view.
- Caveat: a Ninth Circuit ruling on a rival agent six weeks earlier left Amazon's contract claims wide open.