Your AI agent can now move money.

Sequence gives agents programmable financial execution — accounts, rules, and transfers — with the guardrails only you define.

Read the docs
You — Sequence console
Pay Amex
Trigger: MANUAL
Action: next_payment_minimum
Cap: $2,000 / month
Your agent — API
# Trigger the rule
curl -X POST \
api.getsequence.io/api/v1/
rules/rule_01HXYZ.../trigger \
-H "Authorization: ApiKey ..."
# ← exec_01HXYZ9999

Most agents can only advise. Yours can act.

Your agent already knows what move to make. It sees the balance, understands the debt, knows the timing. But without execution capability, it ends every conversation the same way: "You should transfer $400 to your Amex." And then you go do it manually.

Sequence closes that loop. Your agent reads balances, triggers rules, and moves money — not as a suggestion, but as an action. That’s a different category of agent entirely.

Sequence is the missing layer. Your agent gets execution capability. You keep control of what it can do with it.

You define the rules. Your agent executes them.

You — console, once
01
Connect your accounts
Link bank accounts via Plaid, Finicity, Method, or Spinwheel.
02
Define rules
Set triggers, conditions, and actions. This is your financial strategy.
03
Scope your API token
Grant exactly the rules and accounts your agent needs. Nothing more.
guardrail
Your agent — API, on demand
01
Read balances
Check account balances before making decisions.
02
Trigger rules
Execute financial strategy with a single POST request.
03
Audit executions
Every rule run is logged. Full history, always available.

Rules are your financial strategy in code.

01 / 04
01
MANUAL trigger
"On demand, pay my Navient loan — capped at $500/month so it can never overpay."
MANUALnext_payment_minimumPER_MONTH cap
02
ON_FUNDS_TRANSFERRED trigger
"Every time income hits my Chase checking, move 28% to my tax pod."
ON_FUNDS_TRANSFERREDpercentageINCOMING_AMOUNT
03
SCHEDULED trigger
"Distribute $1,000/month across my credit cards, highest APR first — automatically."
SCHEDULEDavalancheMONTHLY
04
MANUAL trigger
"Give my agent a dedicated pod. It spends from there. I top it up via a rule."
MANUALfixed_amountpod

Your agent gets exactly what it needs. Nothing more.

agent-loan-repayment-bot
TRIGGER_RULESrule_01HXYZ5678 (Navient payment rule only)
READ_ACCOUNTSacc_01HABC4567 (checking balance only)
# No MANUAL_TRANSFER permission.# No access to savings pods.# Cannot trigger any other rule.
If your agent is compromised, stolen, or hallucinates — it can only do the one thing you gave it permission to do. That’s the point.

Works wherever your agent lives.

01
MCP

Install the Sequence MCP server. Your AI coding assistant reads balances and triggers rules as tool calls — mid-conversation.

npx @getsequence/mcp-server
02
REST API

Standard REST. Authenticate with your API key. Call from Python, TypeScript, Go, or anywhere else.

curl api.getsequence.io/api/v1/...
03
n8n / Zapier

Use the HTTP request node. Trigger rules on schedule, react to webhooks, chain with other services.

POST /rules/{id}/trigger

From zero to triggered rule in 4 minutes.

curl https://api.getsequence.io/api/v1/accounts \
-H "Authorization: ApiKey YOUR_TOKEN"
A successful response returns your full account list. Your token is valid and scoped correctly.

Built for the cases when things go wrong.

CAP
Transfer caps

PER_TRANSFER, PER_MONTH, PER_YEAR — hard ceilings the rule can never exceed, regardless of what your agent passes.

IDEMPOTENCY
Idempotency keys

Same request, same result. No accidental double-payments from retries or network errors.

AUDIT
Execution audit log

Every rule run is logged with full detail — what fired, when, what it transferred, and why.

GATE
Human review gate

New and updated rules require a human to re-enable them in the console. Agents cannot self-modify their rules.

Give your agent a financial brain.

Set up takes 20 minutes. Connect your accounts, define your first rule, generate an API token. Your agent handles the rest.

Read the docs
accounts → rule → token → agent