Walletguide for builders and agents
Everything the Walletguide app can do to your data, over a REST API, a CLI and an MCP server. One OpenAPI document behind all three.
Walletguide tracks what you own and what moves through it: bank and brokerage accounts, property, crypto, the transactions behind them, and the net worth and cash flow that come out. Everything the app does to that data, it does over an API you can use too.
There are three ways in, and they are the same surface underneath.
REST API
100 endpoints, an OpenAPI 3.1 document, and a playground you can run against your own wallet.
MCP
Connect Claude or another agent, hosted over OAuth or locally over stdio.
CLI
npx walletguide. Every route as a command, tables in a terminal and JSON in a pipe.
Start here
One document, three surfaces
The API is described by an OpenAPI 3.1 document. The CLI's commands, the MCP server's tools and every page of the reference are generated from it at build time. Nothing is hand-maintained, so a new route shows up in all three at once and none of them can quietly fall behind.
That is also why the names line up. GET /wallets/{walletId}/assets is the tool assets_list and the command walletguide assets list. Learn one and you can guess the others.
What it will not do
Walletguide reads from banks and brokers. It does not move money, and nothing here can. Every call is scoped to one wallet and needs a credential; there is no anonymous read.