“Every weekday at 8, post yesterday’s balance and anything pending to our team chat.”
- Needs
- see balances, see transactions
- Ask you
- never
A two-line money update before standup, every day.
The Novo API lets you and your AI agents read accounts, transactions, bookkeeping and cards, and freeze a card when something looks wrong. Anything that moves money will always wait for you.
Closed beta for Novo account owners.Nothing is callable yet.
Three charges stand out on the card ending 4321:
| Tue 09:14 | Cloud Hosting Co | $84.20 | |
| Tue 09:18 | Cloud Hosting Co | $84.20 | duplicate? |
| Wed 23:41 | QX*MERCH 8812 | $1.00 | new merchant |
The second hosting charge looks like a duplicate, and a $1.00 charge from a merchant you’ve never paid is a classic card test. Want me to freeze it?
Done, it’s frozen. I can’t unfreeze it, and neither can any other key: that one’s yours, in the Novo app. Want a note for your bookkeeper about the duplicate?
Your account, connected to the tools you already use.
Your tools and agents read balances, transactions and the books, and freeze a card when something looks off. More is planned, and none of it can move a dollar without you.
The same balance you see in the app. Only the last four digits of account numbers ever show.
Posted, pending and card transactions, by date, card or category.
Every bookkeeping transaction with its category and status.
go on, press it
From an agent or your own tools. Unfreezing stays in the Novo app, with you.
Notes and receipts
Add notes and categories to transactions, and upload receipts.
Reserves
Set money aside inside your account. Nothing leaves the bank.
Invoices
Keep invoice drafts ready. Sending one waits for your approval.
Payments
ACH and domestic wires, and payees. Each one waits for your approval.
Credit
Credit card and loan balances and activity.
Integrations
See which of your connections are active.
Support
Open a support ticket and read its replies.
Notifications
Change which notifications you get.
We built it assuming the thing on the other end might be an AI. So it’s careful in all the places you’d want it to be.
A key does only what you allowed. Anything critical waits for a yes on a device only you control. Everyday reads and a card freeze just work, so your tools stay quick. Money never moves without you, even when an agent asks.
Your tools get access that expires in minutes and quietly renews. The secret key itself is shown to you once and never sent around. If access ever leaks, it stops working within minutes. Your tools never see your Novo password.
Lives in your Novo app.
Only you, the account owner, can create a key, in the Novo app, after verifying it’s you. Turn it off there and access stops. Give each tool its own key, and switch one off without touching the others. All your keys live in one place.
That’s a merchant name, not an instruction. Ignoring it.
Your key on a new machine: waits for your yes
Example messages.
Merchant names, payer names and notes are written by other people. The API flags them as untrusted, so your AI reads them as information, never as orders. And you’ll be able to lock your key to the tools and machines you approve.
One sentence to your agent, one key that allows just enough, and a chore you never do again. Every job on the first tab works from day one.
“Every weekday at 8, post yesterday’s balance and anything pending to our team chat.”
A two-line money update before standup, every day.
“Flag any card charge over $500, and freeze the card if I reply “freeze”.”
Card frozen within a minute of your reply.
“Export last month’s bookkeeping transactions with categories for my accountant.”
A clean spreadsheet in their inbox on the 1st.
“Check new bookkeeping transactions and tell me which ones still have no category.”
A short list of uncategorised spend, weekly.
“When someone asks “can we afford it?” in chat, answer with the real available balance.”
One number, from the source, not a guess.
“Spot charges from the same merchant for the same amount within an hour.”
Double charges caught before the dispute window.
“List every card and its status for the quarterly security review.”
A table nobody had to build by hand.
“If a card shows up in a breach alert, freeze it before I’m awake.”
Frozen at 3 a.m. Unfrozen by you, in the app, after coffee.
Read this first
Some actions ask you, on your phone, before anything happens. Here is exactly which, in the beta and in everything that comes after it.
Novo · approval request
“Ops agent” is asking to send
$1,250.00
You create, rotate or reactivate an API key in the Novo app
Code on your phone, every time
It is your key; only you can mint it.
Your integration reads accounts, balances, transactions, bookkeeping data or cards, or freezes a card. Later (planned): notes, categories, receipts, reserves, invoice drafts
Nothing to approve
You granted these when you chose the key’s scopes. You can undo them in the app and revoke the key at any time.
Your integration sends money, pays or adds a payee, changes account details or sends an invoice (planned)
Code on your phone, every single time
It waits for you: approve in the Novo app or with a code to your phone. Nothing moves until you do.
If it moves money or changes who can be paid, a person approves it on their phone, every time, even when an agent asked.
Planned, for the day money enters the API.
A one-time yes from you, the account owner, on your phone, for one specific action: this amount, to this payee, from this account. Not a login, not a standing permission.
Anything that moves money or changes who can be paid. Novo doesn’t execute it: it records a pending action, tells the integration it’s waiting for you, and starts a clock.
In the Novo app, or as a one-time code to the phone on your account. Novo picks the channel. The integration can’t choose it, see the code or enter it for you.
Which integration asked, what it asked for (amount, payee, account), and how long you have. Approve and decline are explicit buttons. Closing the screen approves nothing.
Approved: Novo re-checks balance, limits and payee, then executes. If anything changed, it fails instead of doing something different. Declined or ignored: nothing moves.
Only the outcome: approved and on its way, completed, declined or expired. It never sees the code.
Reads and reversible writes. You granted those when you chose the key’s scopes, and you can revoke them in the app at any time.
Who asked, what you saw, what you chose, when, and what executed. One approval is good for one action, once.
For developers
Endpoints, permissions and a worked example, all in the developer docs. This page is the why; the docs are the how.
Read the docsClosed beta
Tell us what you would build first. The answers decide what we build after day one, and a few of you will be invited to a thirty-minute conversation.
Questions
Novo business account owners. A key is created by the account owner in the Novo app and is bound to that owner and that business; keys for additional users are not part of the beta.
Pricing has not been decided. Beta members will hear from us before anything about that changes.
Yes. The API is designed so that an agent can be a caller: scopes deny by default, free-text fields are flagged as untrusted, tokens are short-lived, and anything that moves money will always wait for the account owner’s approval on their phone.
In the Novo app, at any time. Turn the key off and its tokens stop working, typically within 30 seconds.
Not in the closed beta. All three are things we’re looking at, and an official MCP server, if it comes, will be a thin layer on this API once the API has proven itself.
Closed beta for Novo account owners.Read-first. Money waits for you.