Why this exists
For two years now we’ve been watching the same scene play out in our user base. Someone builds an AI agent that’s genuinely useful, gets it parsing emails or classifying transactions or running a workflow they actually rely on, and then they hit a wall. The wall is always the same: the agent has a decision but can’t actually act on it. It writes the email, drafts the budget, or recommends a transfer between accounts, but the actual money movement still requires the user to switch tabs, open a bank app, and click through it manually.
That’s the part Sequence has handled for our users on the front end for a while now: income lands and money flows, rules fire, pods fill. The thing is, until today, every one of those rules lived inside our app. You couldn’t trigger them from Claude, you couldn’t have an agent fetch a live balance, you couldn’t ask Sequence to move money from outside the dashboard.
People kept asking. So we finally built it.
What you can actually do, in plain English
Here’s what your code can do once you have an API key.
First, it can read anything you’d see in the app. Live balances on every account you’ve linked, every transfer that’s ever happened, every transaction on a Sequence card, every rule you’ve built, every time a rule fired and what it did. Whatever’s in the app, your code can pull it. For instance, you could have a Claude agent answer “what’s my total liquid cash this week?” by reading Chase, Marcus, and your business checking in a single call, then writing a one-paragraph summary into your morning Slack.
Second, it can move money on demand. You can tell Sequence to move a specific amount from one of your accounts to another, and the API does the actual transfer. The real thing, on real rails, between real accounts. What this lets you build: an agent that reads a contractor’s invoice from your inbox and, when you tap “pay” in WhatsApp, fires $750 straight from your business checking to that contractor’s bank account.
Third, it can build and modify rules from code. You can create a new automation rule, update an existing one, or delete the ones you don’t need anymore, all without opening the app. Say you onboard a new freelancer to your roster: an n8n flow can create a “Pay {their name}” rule automatically, with their bank info and a default amount baked in, and you never have to touch Sequence yourself.
Fourth, it can fire any rule you’ve already set up. Whatever you’ve built in your Sequence Map is now triggerable from outside: your weekly allowance run, your quarterly tax payment, your invoice payment, your team payouts. They all stay where they are with the same guardrails you set, but anything that can make an API call can now fire them. Picture a Notion automation that pings the API every Friday at 4pm and fires your weekly clipper payout rule with that week’s variable amount. Same rule you built in the app, just a new way to trigger it.
And fifth, it can spin up new accounts: savings pods, income sources, external bank links, all created from your code. So when a new client onboards through your intake form, your CRM can quietly create a dedicated income source account in Sequence, and their payments land in the right bucket from day one.
That’s the whole API. If you’ve used Sequence before, this is the same product, just programmable now.
What this looks like in practice
Take a small example. Say you run a creative agency and you pay six freelancers every two weeks, with amounts varying based on hours worked. Today the loop probably looks something like this: you pull hours from a spreadsheet or time tracker, calculate what each person is owed, open your bank app, manually trigger six transfers, and then send each freelancer a Slack message to tell them they’ve been paid. It takes most of a Sunday.
With the API, that whole loop runs without you. Your spreadsheet (or an n8n flow, or a Claude agent reading the time tracker directly) calculates the amounts and tells Sequence to move them. Slack pings everyone automatically. You never open a bank app, and the total elapsed time is something like a minute.
That’s one example, we’ve written up many more.
Why this is different from other financial APIs
Every other financial API you’ve used reads data. Plaid, Yodlee, and Teller are how apps see your accounts. They don’t move money, and that’s not what they were built for.
Sequence moves money. Real ACH transfers, between real bank accounts, on rails that have been quietly running for our users for a while now. The only thing new today is that they’re exposed.
There are other tools that move money programmatically. QuickBooks and Wave handle payments, but they’re accounting software first — the money movement is a byproduct of the bookkeeping, not something you can trigger from code. Platforms like Melio or Bill.com let small businesses pay vendors, but they’re built around human approval workflows, not APIs an agent can call. With Sequence, the accounts and rules are already there because your user has already done that onboarding. You’re plugging into something that’s already running.
That’s the real difference. Not “we move money too,” but “we move money on top of what your user already trusts.”
What comes next
This is release one. There’s a lot more we want to expose and we’re shipping fast, but the quickest way to get something prioritized is just to ask for it. Reply to the launch email or send us a note. We read everything.
Where to start
Sequence API reference: https://api.getsequence.io/platform/. Knowledge base: support.getsequence.io. Share what you build.