Metering Offer · meter.witness
Hive verifies meter and billing data with signed cryptographic receipts, and takes 15% of whatever you recover.
15% of recovered overcharges
Billing runs on numbers nobody can check after the fact. A meter reports a register reading, and a rating engine turns that reading into money. By the time someone disputes the bill, the original reading is a row in a database that anyone with write access could have changed, and the firmware and calibration settings that produced it are long gone.
So disputes turn into arguments about whose spreadsheet to believe. Regulators ask for evidence that was never captured, and credits get issued on estimates because nobody can reconstruct the actual chain.
You probably know roughly where your exposure sits. What you're missing is proof you can hand to a regulator, a customer, or a vendor without asking anyone to take your word for it.
We take your metering and billing records and verify them against a signed receipt chain called
meter.witness. The receipt commits to meter identity, the
device key, the firmware hash, the calibration coefficients, and a cumulative register reading. A
later reading gets checked against that committed chain instead of being trusted on sight.
meter.witness is built and passes 30 of 30 checks today. Hive's underlying method is
patent pending.
Where the numbers don't reconcile, you get a receipt that shows which commitment broke and when. You use the findings however you want: internal remediation, a regulatory response, a customer credit run, or a vendor dispute. We don't need to touch your billing system to run the check, and we don't need a procurement cycle to start.
Ofgem secured customer compensation from ten suppliers over a technical overcharging error, and all ten have open remediation work (Ofgem press release).
The hard part in that work is proving what each meter actually read, on which firmware, under which calibration. That's the gap we fill.
One audit of $34M of enterprise AI spend found roughly $1.7M of billing errors, and about 80% of that was credited back by the providers (Vaudit announcement, BusinessWire). For scale, FinOps survey respondents represent over $69B of public cloud spend, and more than 20 organizations in that group spend over $1B a year (FinOps Foundation 2025 report data).
Token and instance metering has the same weakness as a gas meter: you get a usage number and no way to audit how it was produced. We verify the records you were billed on and give you signed artifacts you can put in front of your vendor.
Nothing if nothing is recovered. No setup fee, no minimum, no license.
There's no software to buy, so there's no budget line to open. Sign a short contingency agreement and we start.
meter.witness receipt chain over the records in scope, committing meter
identity, device key, firmware hash, calibration coefficients, and cumulative register reading.We won't tell you what you'll recover, and we won't promise a finding. Some record sets check out clean, and if yours does, you pay us nothing.
Hive never fabricates a receipt. If a receipt covers simulated or reconstructed data rather than production records, both the receipt and the report say so in plain language on the face of the artifact. Findings we can't back with a verifiable receipt don't go in the report.
The receipt itself carries a boundary too. Read what a
meter.witness receipt does not establish before you rely
on one.
Send us a sample of your metering or billing records and we'll tell you whether there's something worth verifying. Reach us through the contact page at thehiveryiq.com.
Patent pending. Hive Civilization, The Hivery, Inc.