Check a cost statement yourself
A cost statement is only worth relying on if someone who does not trust Provantix can check it. This page walks through checking one, and through what happens when someone changes a figure.
The statement here is a sample. It is one month (October 2026) of made-up AI spend for a fictional "Sample organization": five agents, about 67,000 model calls and 7,360 dollars, with a runaway loop in the middle of the month and one agent nobody owns. It is built by the same code that builds a real statement, from a fictional provider and made-up prices, and signed with a sample key made for it. It is not a Provantix key, and it is not from a customer or from the demo organization. It is the same data the home page's charts and statement preview are drawn from, so you can check what you saw there.
Download
provantix-sample-cost-statement.zip(hash in.sha256): the sample statement.provantix-sample-cost-statement-altered.zip(hash in.sha256): the same statement after one figure was changed and the manifest rebuilt to match.provantix-sample-export-keys.json: the sample's public key, for the command line below. It is a sample key and is never a substitute for Provantix's published keys.- The verification kit: the Node and Python verifiers, the format specification, a smaller pair of statement samples and what the verifier prints for each.
On the home page, or in the browser
The home page has a Verify the sample statement section that runs the real verifier on these two files, in your browser, without sending anything anywhere.
To use the public verifier yourself, open provantix.tech/verify, press Choose zip or files and pick a downloaded zip (keep it zipped), or drag the zip anywhere on the page. The result appears below the boxes. (The "Open a share link" box beside it is for links people share from the product, not for files.)
For the good sample you will see every file hash match and a Cost statement panel saying the cells add up to the stated total. The verify page's authenticity line will not say Provantix issued it, because the sample is signed with a sample key and not a published Provantix key. For the altered sample, every file hash still matches, because the manifest was rebuilt, and the Cost statement panel fails and names which figures no longer equal their cells.
On the command line
With the verifier from the kit (Node 20 or later, nothing to install) and the sample key file, from the folder holding both zips unpacked into folders:
node verifier/verify-export.mjs statement --keys provantix-sample-export-keys.json
node verifier/verify-export.mjs statement-altered --keys provantix-sample-export-keys.json
The first ends "export verified" and exits 0. The second ends "export FAILED verification" and exits 1. python3 verifier/python/verify_export.py statement gives the same checks (it checks files and figures; the Node verifier also checks the signature).
What is checked
Every file in the bundle against the signed manifest, the signature against the key you pass, and then the figures themselves, added up from statement/cells.json:
- the cells add up to the stated total;
- the totals by provider and model equal the cells;
- each allocation (department, cost center, product, agent) equals the cells and adds up to the total, with anything unallocated as its own line;
- the cover total equals the total;
- the per-department chargeback files add up to the total.
What happens when a figure is changed
In the altered sample one cell's cost was raised by one dollar. Someone changing a statement would then rebuild the manifest so each file hash matches. Two things still give it away:
- The arithmetic fails. The cells now add up to one dollar more than the statement says, and the totals by provider and model and each allocation no longer equal their cells. This works on a statement that carries no signature at all.
- The signature fails. The signature was made over the original manifest. A forger can rebuild the hashes but cannot sign, so the verifier reports that the manifest is not the file that was signed.
Before the arithmetic check, a statement with a rebuilt manifest and no signature to check would have passed.
What a pass does not mean
It shows the files are the ones that were signed and that the stated totals are what the cells add up to. It does not show the cells are the right figures: they are estimates frozen when the month was closed, from the organization's own price table. A provider's own figures, where the statement carries them, are what the provider reported when they were fetched, and are not an invoice. The sample connects no provider, and its first page says so. The statement is cost evidence that supports an audit. It is not an audited financial statement.
See The cost statement for what each section contains and How verification works for the rest of the checks.