# Flip: a money manager people use in iMessage

Canonical: https://mudpie.ai/companies/flip/
Breadcrumb: [Home](https://mudpie.ai/) / [Companies](https://mudpie.ai/companies/) / [Flip: a money manager people use in iMessage](https://mudpie.ai/companies/flip/)
Author: Ali Abouelatta (https://mudpie.ai/authors/ali-abouelatta/)
Published: 2026-09-20
Updated: 2026-09-20
Research type: Company profile
Method: Public-source research. Official Speedrun and company pages checked September 20, 2026. Product claims are attributed to their sources.

Flip puts personal-finance chores in an iMessage conversation and exposes an agent API for approved workflows.

## What it does

The public developer page describes a public MCP server, CLI and agent API with read-mostly tools across accounts, transactions and bills; writes are gated by user approvals and authentication. The homepage frames the consumer product as an iMessage conversation.

## Buyer and task

Consumers who want personal-finance actions in text, plus developers integrating approved workflows.

## Workflow boundaries

The public pages do not establish a banking connection, transaction-safety or investment result. The developer page says sign-in and OTP setup are required for user access.

## What I would ask

Ask exactly which actions can move money, where user approval occurs, and how an agent’s access is revoked after a session.

## Why it fits

Flip’s public product makes money-management actions available in an iMessage conversation, then exposes the same surface to agents through an MCP server, CLI and agent API. The developer page says the tools are read-mostly across accounts, transactions, bills and recurring spend, with writes gated behind user approvals. It also describes per-user SMS-OTP authentication, one-time connection links and the need for the user to finish bank or provider setup.

That is a specific architecture for a personal-finance assistant: a text interface for a person, a machine-readable surface for an agent and an approval boundary around actions that change financial state. The right buyer question is not whether a model can call a banking tool; it is whether the user can understand exactly what will happen, approve it at the right moment and revoke access cleanly. The public page names about 90 tools and connected surfaces, but the public material does not establish a banking connection, investment result or transaction safety.

The product also says some website sign-ins happen through a cloud browser and that the user completes the site’s own sign-in and two-factor step on a phone. That is a useful control distinction to verify in a real security review.

## Quick facts

| Field | Sourced detail |
| --- | --- |
| Buyer | Consumers and developers building approved finance workflows |
| User surface | iMessage money manager |
| Agent surface | Streamable-HTTP MCP, CLI and agent API |
| Action boundary | Read-mostly tools; writes described as requiring user approval |

## Sources checked

[official Speedrun profile](https://speedrun.a16z.com/companies/flip) · [company homepage](https://fliptexts.com/) · [source page](https://fliptexts.com/developers) · [source page](https://fliptexts.com/privacy)

Sources checked — September 20, 2026.


## Author disclosure

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.