PocketSmith, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your PocketSmith account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Accounting
- Connects with a key
- 14 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What PocketSmith is
PocketSmith is a personal finance platform for tracking accounts and transactions, managing budgets, and forecasting financial outcomes.
You paste in a key from your own PocketSmith account. It is kept encrypted, and you can withdraw it from inside PocketSmith whenever you like.
One message in, the work done in PocketSmith.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in PocketSmith. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own PocketSmith account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in PocketSmith
These are the ready-made tools your AI employee already has in PocketSmith. It is not limited to them, but it never has to be taught these.
- Create CategoryCreate one category for a PocketSmith user with optional hierarchy and budgeting behavior.
- Create TransactionCreate one transaction in a specified transaction account and return the created financial record.
- Get BudgetReturn a PocketSmith user's current category-level actual and forecast budget analysis. During probing, this read coincided with forecast cache access/update timestamps changing to
- Get Budget SummaryAnalyze the user's combined income and expense budget over a required date range and period interval.
- Get Current UserReturn the PocketSmith user authorized by the connected developer key, including the user ID needed by user-scoped tools.
- Get TransactionReturn one PocketSmith transaction by ID with its amount, date, payee, category, labels, and review state.
- List AccountsReturn all financial accounts belonging to a PocketSmith user, including account, primary transaction-account, and scenario IDs.
- List CategoriesReturn all categories belonging to a PocketSmith user, including hierarchy and budgeting flags.
- List Transaction AccountsReturn the transaction accounts belonging to a PocketSmith user, including IDs and balances needed to create and query transactions.
- List TransactionsReturn one page of a user's transactions with optional date, state, type, and keyword filters, plus a cursor for the next page.
- Update AccountUpdate selected metadata on one financial account without deleting it or changing transaction-account balances.
- Update CategoryUpdate selected hierarchy, display, and budgeting fields on one category without deleting it.
- Update TransactionUpdate selected fields on one existing transaction without deleting or splitting it.
- Update TransactionsUpdate 1-20 distinct transactions sequentially. The operation is not atomic: successful updates are not rolled back, each item has an explicit outcome, and processing stops after a
You stay the boss of your PocketSmith account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own PocketSmith account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in PocketSmith is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in PocketSmith and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about PocketSmith
- Can an AI employee really work inside PocketSmith?
- Yes. It signs in to your own PocketSmith account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of PocketSmith?
- No. Nothing moves and nothing is replaced. Your records stay in PocketSmith, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my PocketSmith account?
- You paste in a key from your own PocketSmith account. It is kept encrypted, and you can withdraw it from inside PocketSmith whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in PocketSmith?
- It has 14 ready-made tools in PocketSmith today, among them Create Category, Create Transaction and Get Budget. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use PocketSmith and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in PocketSmith and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in PocketSmith?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in PocketSmith is written down with what it did and when.