Invest1 publisher2 min readPublished
Meta hands Muse's connector work to outside developers ten days after launch
Ten days after shipping its personal agent, Meta opened a portal where outside developers can build Muse connectors, each one gated on Meta's functional, security and legal review and on a separate user approval.
The Investor · Invest desk

What happened
- Meta launched Muse, a personal AI agent that sits on top of a user's apps and acts on their behalf across Gmail, Google Calendar and Spotify, on September 8, 2026.
- On September 18 Mark Zuckerberg announced a developer submission portal at muse.ai/platform where third parties can build and submit custom Muse connectors for review.
- New connectors went live the same day as the announcement.
- Submitted connectors have to meet Meta's functional, security and legal requirements before anything goes live.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- constraint A developer is being asked to commit maintenance engineering to a platform whose fees and revenue split are not public, so the build cannot be priced before the work starts.
- decision Because each connection is approved separately, a connector's reach is assembled one user consent at a time, and no arrangement with Meta delivers that distribution in one stroke.
- exposure Any business built on a Muse connector sits inside Meta's review queue, which decides what goes live and can decide what stays there.
- capability If Stripe is sitting in as a payment layer, connectors could move money, and the unpublished revenue share becomes a take rate on transactions instead of a listing fee.
Ten days separate the September 8 launch from the September 18 portal [11], and in that window the only things Muse could reach were the connections Meta built itself: Gmail, Google Calendar, Spotify [2]. Everything past those is outside engineering now, submitted at muse.ai/platform and held until it clears Meta's functional, security and legal requirements [3][6].
The consumer side has a published price. Power is $20 a month and Maximum is $100 a month, each buying progressively higher usage limits [7], which works out to $240 and $1,200 a year [12], the top tier at five times the lower one [13]. Usage limits are what Meta is selling. A bigger connector library produces more calls against those limits, and the engineering for it is being solicited from people who, according to CryptoBriefing, have not been told the agreement terms, the fees, the revenue sharing arrangements, or how long review takes [9].
A connector is not a one-time build. Upstream APIs change and tokens expire, and the developer carries that support load for as long as the connection is live.
Individual authorization is how Meta handles trust here: a user approves Gmail without approving Spotify, and nobody grants blanket access to everything at once [5]. For a developer that means reach accumulates one consent at a time. No single arrangement with Meta substitutes for it.
Then there is Stripe. CryptoBriefing says its research indicates Stripe is involved as a payment facilitation layer, and points toward connectors that could transact rather than only read and summarize [10]. If that holds, the unpublished revenue split is the commercial question in the whole programme, because a connector that moves money has a take rate attached to it. On the current record, Stripe's role rests on one publication's reading.
One way to read the timing is that the personal-agent contest is settled by how many things the agent can touch, and Meta is buying that surface area with labour it does not have to hire. Another is that a review gate with no published terms keeps serious counterparties away, and the portal fills with thin connectors that few users approve. A third is that payments were always the point, in which case the fee schedule matters more than the connector count. The evidence supports a narrower statement: Meta opened submissions before publishing what a submission is worth. Muse already runs on iOS, Android, the web and WhatsApp, with AI glasses on the roadmap [8].
What to watch
- Publication of the connector agreement: fee schedule, revenue split, and review turnaround times.
- Whether any live Muse connector can take a payment, which would put Stripe's role beyond one publication's reading.
- Whether Meta discloses how many submitted connectors clear review, and how many users approve each one.