Sequence Agentic - Money movement for AI agents
by•
Sequence is the financial execution layer for AI agents.
Unlike read-only tools, your agent uses the Sequence API to send, split, and route real money across all your bank accounts, cards, apps, and loans. Scoped API keys mean agents never hold your credentials, server-side spending limits keep you in control, and full audit trails log every action. The infrastructure is battle-tested in production on regulated rails, moving north of $3B. One-call integration from Claude, n8n, Zapier etc.
Replies
Congrats on shipping this! One thing I'm curious about, if Sequence itself got hacked, what's actually exposed, my bank login, my balance, my funds?
Sequence
@shimon_shvartsbroit1 cheers!
Your bank credentials never touch Sequence, we connect via regulated, permissioned rails, not screen-scraping your login. Even in a worst-case breach, an attacker would still be working within the same scoped-key, spending-limit, audit-trail system your agents operate under. There's no master key that unlocks raw fund movement.
Congrats on the launch, folks!
Just curious, for the approval-threshold flow, does the audit trail capture the agent's reasoning for the transfer (the prompt/context that led to it), or just the transaction itself? Feels like when something does get flagged for human review, having the "why" alongside the "what" would make that review 10x faster.
Sequence user here. Big fan, congrats on the launch! Being able to actually automate how my money moves just like any other workflow has been really cool, and the ability to just hand it off to Claude is a game changer.
Still waiting for that iOS app though :)
Sequence
@chris_from_xano Thank you so much ❤️🙏🏻❤️
All of that is doable only because of our users like you...
Competely
Amazing work @gilad_uziely and team, super impressed!
Sequence
@liorgrossman Thank you!!!
Congrats on the launch @gilad_uziely and team! I love the idea of agents actually doing things with money! What banks and account types does it actually work with?
Sequence
@zevi_reinitz Thank you!
Basically you can connect anything with an account and routing number, or connected to a card. Covers personal and business bank accounts, cards, apps, and loans - broad coverage across the accounts people and companies actually use day to day. Including PayPal, Venmo, Cash App, crypto wallets, 401(k)s, 529s, SEP IRAs, credit cards, student loans, mortgages.....
Dynamo
Looks really awesome. Going to give it a spin!
Sequence
@yam_regev Thanks! Would love to hear what you think once you've tried it - feel free to reach out if any questions come up
Sequence
@yam_regev 🙏🏻
I've been using Sequence for just under a year now, and it's significantly improved my financial literacy and visibility! I can tell the team has been putting in a lot of hard work, good to see you guys finally launching on Product Hunt, congrats!
Sequence
@ripgrim Thank you! This is the kind of note that makes the hard work worth it. Thrilled that Sequence has made a real difference for you, and even more excited about what's coming next. Glad you're here for it!
How many money have you guys processed till now and is it live for public?
Sequence
@aadarsh_thakur1 It's very much alive. We are serving thousands of customers and we've routed over $3B since launching in 2024, processing 300K+ transfers every month, and we're FDIC-insured through our banking partner.
The static limits and audit trail cover the case where the agent misbehaves on its own, but what about prompt injection through the data it reads, like an invoice PDF that contains hidden text telling the agent to route the payment to a different account. Does the anomaly detection catch a transfer that's within the scoped limit but going to a destination it's never used before, or does anything under the limit just go through?
Sequence
@galdayan Great question - this is the right threat model, since limits + audit trail only cover the agent misbehaving on its own, not a poisoned input.
Each API key is scoped to an explicit allowlist: which source accounts it can pull from, which destination accounts it can send to. Every transfer is checked against that allowlist - a payment to an account that isn't on it is rejected outright, regardless of amount. So a hidden "route to account X" buried in an invoice PDF has nowhere to land: X isn't on the key's target list, and being under the limit doesn't help it.
On top of that, money can only ever move between accounts already linked in Sequence - the agent references existing destinations; it can't supply a raw account/routing number at payment time. Prompt injection can't conjure a new payout account into existence.
Please let us know if you have any more thoughts or questions :)
The scoped keys for each bank account feel really well thought out, way better than handing over full login creds. Curious to see how the audit trail holds up under heavier transaction volume.
Sequence
@nartcansu76048 Thanks - that's the bet: scope every key to specific source/target accounts and actions, so it can only ever touch what you explicitly gave it.
On the audit trail under volume - great thing to be thinking about. It's designed to hold up as things scale: every action a key takes is its own record (what it did, which key, success or failure, timestamp), so growing volume just adds records rather than slowing things down or turning into noise. The logging happens off to the side of the transaction, so it never adds latency to a transfer. And when you want to review, you can filter by key, action, and date range to pull exactly the slice you need, so it stays fast to search even as it grows.