Overview
Everything the Walletguide app can do to your data, over a REST API, a CLI and an MCP server — all generated from one OpenAPI document.
Walletguide has no private API. The app talks to the same public routes you do.
REST API
About a hundred endpoints, an OpenAPI 3.1 document, and a playground you can run against your own wallet.
CLI
npx walletguide. Every route as a command, tables in a terminal and JSON in a pipe.
MCP
Connect Claude or another agent, hosted over OAuth or locally over stdio.
One document, three surfaces
The OpenAPI 3.1 document is generated from the route definitions themselves. The CLI's commands, the MCP server's tools and every page of the endpoint reference are then generated from it, at build time.
Nothing in that chain is hand-maintained, which is why the three agree and why a new route reaches all of them at once.
It also means 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.
Which one to use
| You are | Use |
|---|---|
| Writing a script or a CI job | The CLI with an API key |
| Building software against someone else's wallet | The REST API with OAuth |
| Pointing an AI agent at your own money | MCP, read-only to begin with |
| Exploring | The reference — every endpoint has a playground |
The one thing to get right
Ask a data slice for a metric. They compute over the full history on the server and apply the rules raw rows do not carry: splits, transfers between your own accounts, offset categories. Listing transactions and adding them up returns one page of them and no warning that there were more.