Muse 01
Tested on hundreds of simulations
Each scenario is one YAML file. Simulated users try every edge case before a real one does.
Build once.
Ship to every chat.
Let users chat with your product on iMessage & WhatsApp, and use it as an MCP in their ChatGPT, Claude.
Start building
Copied. Give it to your coding agent (Claude Code, Codex, Cursor) and it will do the full setup.
Backed by 
Entrepreneurs First
Ships to
- iMessage
- Claude
- ChatGPT
- MCP
- CLI
For a decade, people used apps.
Dashboards at work. Mobile apps for everything else. Click, tap, fill in the form.
Now they'd rather just chat.
Say what they want, the way they'd text a friend, and get it done right there.
And they chat everywhere.
ChatGPT and Claude. WhatsApp and iMessage. Personal agents like Instinct and Muse. Any MCP client. A terminal.
Flow puts your product in every chat.
One agent, one codebase, every place your users ask.
Start with our open-source framework, built for the interfaces of the future.
Ready for production
Ship it like software.
Tested, traced and improving on its own.
02
Self-improving MCPs and agents
When the model misreads intent or a tool is unclear, Flow fixes it.
03
Traced, every turn
Every model and tool call, timed and kept, so you see why it said what it said.
For consumer apps
WhatsApp and iMessage agents
that feel like texting back.
01
AI orchestrator
A human-like chat experience. It handles shorthand, second thoughts and two languages in one sentence, then does the thing.
02
Built-in memory
It remembers each customer's chat between conversations, on each channel.
03
Voice notes, photos and files
Customers talk, snap and send the way they already do. It understands all of it.
04
Reaches out at the right time
Reminders and follow-ups in each person's time zone, never during quiet hours.
For SaaS
MCPs and CLIs
for ChatGPT, Claude and coding agents.
01
Your product inside Claude and ChatGPT
One MCP server from the same codebase, so people use your product where they already work.
02
A CLI for coding agents
Claude Code and Codex drive your product from the terminal.
03
Each user signs in
OAuth per user, so the agent only sees what they can.
Pricing
Free to start. Pay per user, not per message.
A user is anyone who uses your agent, through an MCP client, a CLI, ChatGPT, Claude or a chat app. No message limits on any plan.
Starter
$0 forever
Launch to real users in minutes.
Get started- Up to 25 users
- MCP, CLI, ChatGPT and Claude
- Shared iMessage and WhatsApp line
- Hosting, AI, Test Suite and Analytics
Pro
Most popular$25$145$55$175$105$225$205$325$505$625 /mo
Scale as your users grow.
Get started- 200 users included, then $0.10 per user
- MCP, CLI, ChatGPT and Claude
- Dedicated WhatsApp line
- Hosting, AI, Test Suite and Analytics
Enterprise
Custom
Our team helps you set it up and launch.
Book a call- Hands-on setup with our team
- Custom pricing and volumes
- Compliance and security review
- Every surface and channel
WhatsApp fees are billed by Meta directly, with no markup.
In every plan
- No message limits
- AI cost included
- Every conversation kept and traced
- No lock-in — your data exports
Who we are
Two people who want your app everywhere your customers chat.
We build Flow ourselves, and we answer every message ourselves. Say hi on LinkedIn or book a call.
Book a call
FAQ Questions,
Questions,
answered.
What is a WhatsApp or Telegram AI agent?
An AI agent lets customers use your app through a conversation. Flow connects to your APIs or MCP server so the agent can answer questions and take actions, such as checking an order or booking an appointment, on WhatsApp or Telegram.
Do I need to have an app already?
No. Point Flow at a web or mobile app, an OpenAPI spec or an MCP server and it builds from that. With none of those, it starts on mock data so you can text your app the same day and swap in real APIs whenever you have them.
Do I need engineers to set it up?
Not to get something live on Telegram — Flow handles the surface, the agent and the deployment. Real data, logged-in actions and payments need your API credentials, which is usually an afternoon for whoever owns your backend.
How does it handle orders and payments?
Actions run against your real systems, never guessed, and every one is logged so you can audit it. Before a release goes out, Flow runs it against hundreds of simulated users on the paths that matter — ordering, rescheduling, refunds, and people changing their mind mid-sentence.
What about platform approvals?
Every surface has its own review and its own rules. Flow prepares and submits what each one asks for, and shows you where each submission stands. The timelines belong to the platforms, so we don't promise them.
Does it remember a customer between conversations?
Yes. On each channel, the bot remembers the customer's chat there, so they can pick up where they left off. You can delete everything it keeps about a customer at any time.
Who owns the conversations and the data?
You do. The threads, the contacts and the orders are yours and export at any time. We do not sell data and we do not train public models on your customers.
What happens after I answer the questions?
Nothing to install and no call to sit through. We read what you told us and come back to you by email, usually within a business day, with what we'd build and what it would take.
The messaging apps around it: WhatsApp, iMessage and Telegram.
Launch your app
where people already chat.
A few questions about what you're starting from. No card, no demo call.