What's new in valkpr
What the product can do, dated, with the numbers it produced. We say which results come from real records and which from test data we made to exercise a case.
2 Oct 2026
Bank statements, cloud bills and books, each payment counted once
valkpr's first version has run on DevClusterAI's own AI spending since 30 Sep. Its first real answer: a runaway agent run on 17 Sep cost $21.01447195 over 3,428 calls, every cent traced to its call. This release teaches it to read the other places money shows up, to notice when two of them describe the same payment, and to answer "what did it cost" as it stood on any past day.
Bank card CSV
Every row becomes a recorded fact. The account's total equals the statement's closing minus opening balance ($1,539.42 on a 38-row September card). Two identical coffees stay two. Importing an overlapping export again writes nothing, and never brings back a row that was reversed. synthetic statement
FOCUS cloud bills
Reads the FinOps FOCUS export that AWS, Azure, Google Cloud and Oracle produce. Billed and effective totals match the file's own sums to the last digit: on the official FinOps 1.0 sample (1,000 rows; AWS, September 2024: $18.0066386184 billed) and on a FOCUS 1.4-shaped file. Rows in units valkpr doesn't know yet are skipped and reported, not guessed. official public sample synthetic 1.4 file
finkpr books
A book from finkpr, our bookkeeping product, comes in as a snapshot file or through its live feed, in either order, and each transaction is written once. One bad transaction is skipped and reported; the rest of the month still comes in. synthetic book
Payments counted once
The bank's record and the book's posting of one payment are linked (33 of them automatically, including bookings a day late or two days early) and counted once. The bank record counts and the posting is shown as a witness. Two payments on the same day for the same amount are never guessed: both stay counted and flagged until a person links them. A payment only one side saw is flagged with its amount after three days. synthetic September
Shared costs split two ways
One AI key used by three projects ($17.71 in a month) is split by fixed shares and by number of calls, side by side, with the difference per project. Each rule adds up to the bill exactly; what a rule leaves unallocated is shown, never spread silently. synthetic usage log
Time travel and corrections
Ask any answer as it stood at a past moment. A disputed charge turns a figure from final to provisional and names the charge. Closing a month freezes a snapshot; a refund that arrives later reopens the answer and says why, while the snapshot still checks out. Undo a wrong match and every snapshot that relied on it is flagged until it is taken again. synthetic Fly.io bills
Was it worth it: decisions and hindsight
A decision is recorded with its options and forecasts. A judgment is recorded with its frame, the alternative it compares against, and the values that would change it; one written after the outcome is marked hindsight. valkpr gives no verdict of its own and scores only forecasts. Failed and refused calls get their own "waste" line in what the money became ($0 in the runaway run: 405 of them, none billed). real run placeholder judgment
Not yet: live bank feeds, e-invoices, CRM, receipts from chat, and use by anyone outside DevClusterAI. Real bank statements and our real book come next.