A ledger with an API, and an agent you can point at it

If you already keep your books in Beancount, you know the two problems: somebody has to run the server, and somebody has to type the postings. This removes both without taking the format away from you.

What you actually get

• A private book, one machine, HTTPS, auto-stopping when idle.
• The ledger as plain text in a git repository. Not exported to text — kept as text.
• An HTTP ledger API scoped to one book by key.
• An MCP server with the tool surface an agent needs: read the ledger, open accounts, add transactions and directives, run BQL, generate reports, view history, revert.
• The Fava web UI behind your login.

The validation gate

Every write runs bean-check before it commits. An entry that does not balance is rejected, not saved and flagged. This is the difference that matters when something automated is doing the writing: your ledger cannot be left in a state that does not add up, because the thing being written to will not accept one.

Bring your own model

Point Claude — or anything that speaks MCP — at the book with your own key and you spend none of our credits. Credits exist for the hosted agent, where the inference is ours to pay for. Using your own is not a downgrade path; it is a supported one.

Run away with it whenever you like

It is a git repository of text files. grep works. git log works. Nothing here is a format anyone has to reverse-engineer in ten years.

Being honest about the gap: the one-click export route is not built yet. The data is not trapped and never was, but the button that hands you a bundle does not exist today, and that is on /roadmap rather than in this paragraph pretending otherwise.