Manus pivot to developer focused API

This is the clearest sign that Manus may be worth more as infrastructure than as an app. A subscription product sells finished tasks to individual users. An SDK sells the underlying workflow engine to other software companies, who can drop Manus into their own product, trigger agents from their own interface, and pay based on usage, which usually expands both volume and distribution.1 2 3 4

• The mechanics matter. Manus already runs tasks by orchestrating browser actions, research steps, code execution, and third party tools. Packaging that as an SDK turns the product from a destination website into a behind the scenes agent layer that other apps can call whenever their users need work done.1 2
• There is a proven pattern for this shift. Supabase used a generous free product to attract developers, then monetized the apps they built through API driven backend usage. Its ARR rose from $30.4M at the end of 2024 to $170M by May 2026 as AI built apps pushed more traffic through its infrastructure.5 6
• The strategic upside is distribution inside other products, not just on Manus.com. Apollo showed the logic from the opposite direction by pushing its data and actions into ChatGPT, Claude, and Perplexity so customers keep using Apollo even when they leave Apollo's own interface.7 8

If Manus executes well, the business should move toward metered agent usage, enterprise integrations, and developer lock in around workflow logic rather than consumer subscriptions alone. That would put it in a bigger market, where winning depends less on having the most viral app and more on becoming the default agent layer other products build on top of.1 3 5 7