Meta’s Muse gains downloads while Amazon challenges its shopping access
A third-party estimate puts the agent at 2.8 million downloads in its first 12 days. Amazon says the service was not authorised to access its store, raising questions about consent and credentials.
The short version
- What happened
- Apptopia estimated 2.8 million Muse downloads in 12 days across its measured footprint; an installation is not a retained user.
- Who it affects
- Consumers could save time on routine tasks but need an intelligible record of what an agent accessed and did in their name.
- What remains unproven
- Apptopia's estimate is third-party download data, not Meta's audited active-user figure.
Keep in mind
Apptopia's estimate is third-party download data, not Meta's audited active-user figure.
Amazon's account of credential and access practices is attributed, and independent technical findings have not been published here.
Multi-source analysis · 2 linked sources. Primary analysed source date: 22 September 2026. Earliest linked supporting source: 24 July 2026.
Read the full report · 3 min The evidence, methods, implications and limitations
Rapid reach, uncertain retention
Reuters reports that Meta's Muse assistant, launched on 8 September, can handle multi-step work including email, travel and transactions. Apptopia estimated 2.8 million app downloads during the first 12 days, a measure of installations rather than regular use or completed tasks. The iOS and Android app was available in the United States and Canada at the time of Reuters' report. Meta's own earlier description of agent features explains the intended capabilities but is a product claim.
Investors see possible subscription revenue from a free product with paid tiers. Those forecasts rely on assumptions about adoption and conversion that have not yet been observed. Download totals can be shaped by promotion, curiosity and replacement installs; they cannot establish trust, accuracy, user benefit or sustainable revenue without retention and task-outcome data.[1][2]
Amazon's objection
Amazon said it had not authorised Muse to access its store and had asked Meta to remove the retailer from the experience. It alleged the agent appeared to capture and store customer credentials, scrape account data and fail to identify itself when entering customer accounts. These are Amazon's allegations as reported by Reuters; the article does not establish independently how every session or credential is handled.
A user may want an agent to shop on their behalf, while a platform may restrict automated access to protect accounts, commercial arrangements and service reliability. The resulting conflict is not solved by saying the user clicked a button. Clear disclosure should specify what data an agent sees, what actions require confirmation, how credentials are protected and which services decline access.[1]
What a useful test would show
Independent evaluation should track successful tasks, errors, unwanted actions, reversals, credential handling and user understanding across a representative sample. Retailer cooperation would make consent and accountability easier to inspect. Where an agent is blocked, it should say so rather than silently attempt another route or leave a user thinking a purchase has been made.
Muse illustrates a broader shift from answering questions to taking action in other systems. That creates real convenience, but also disputes over authorisation and responsibility. The early audience numbers and Amazon's challenge should be read together: distribution can arrive quickly, while operational rules are still being negotiated.[1][2]