Your agents now triage requests, review contracts, run compliance checks, and, with your card network partner, execute payments on their own. And your newest product counts the fastest-growing line in business spend. Both of those rest on records someone else wrote about themselves. Hive signs the decision and the delivery, so the numbers and the approvals verify without anyone's word.
You built the product that finally shows AI spend in one place, connected through billing APIs, reading only cost and usage, never the prompts. But each figure inside it is still provider-reported, the vendor counting its own sales. It is the only major category in corporate spend with no independent record. Switch on receipts and see what the numbers do.
Your own research says it plainly: an agent runs like a meter, and each step it chooses to take is another charge. Approval happens at the top. The spending happens after, out of anyone's sight. Set a ceiling and watch what a signed hold does that a dashboard alert cannot.
Hive forms no opinion about your customers' vendors, budgets, or risk appetite. It sizes how much proof a decision needs, records provenance, and signs it. Your customer sets the floor, and a floor can only get stricter, never looser.
Controllers, AP, and procurement agents decide, and their decisions become commitments. Each one gets a signed record: which model, which policy floor, cleared or held, sealed before the money moves.
An autonomous payment is the one action nobody can walk back. A receipt above the authorization proves the rule ran first, and a held payment proves the limit worked.
Receipted usage turns provider-reported figures into counts the buyer can check, and gives you the one thing a dashboard alone cannot: numbers that survive a dispute.
When an agent reads a contract and recommends, the recommendation is evidence in a later negotiation. Signed the moment it was made, not reconstructed after.
Every controller you serve eventually answers "who approved this, and on what basis?" The exam becomes a query, one signed bundle, verifiable offline.
New markets mean new supervisors reading the same records. Evidence produced continuously beats evidence assembled after the request. It exists before anyone asks.
The first step is small: point one agent decision at the protected route and see what comes back. No integration, no change to card rails or ledgers, no access to customer data. The proof verifies offline today, on a post-quantum standard, by anyone you hand it to.
These receipts add a check of one corporate card action against its delegated control and a continuous record of the receipted run that led to it. They are deployed and open to verify, so the runs below are live checks, not mocks.
This receipt gives your controls team a specific way to inspect one agent initiated card charge. It compares the charge amount, currency, timing, and scope with the constraints in one authority receipt signed before that charge was authorized. The service recomputes the finding from the comparison instead of relying on a result supplied by the caller. Finance, compliance, risk, and legal can see the stated control beside the charge under review. The record can support a review without becoming part of the card rail or ledger.
What it does not do. It does not establish that the cardholder granted the authority, that the agent is genuine, that any network authorized or settled the charge, that goods or services arrived, or that displayed terms were read. It is not payment authorization and holds no cardholder credential; no card network, issuer, or regulator currently recognises it as authentication data, compelling evidence, or a liability shift; it cannot deny, resolve, or affect a dispute, limit rights under Regulation E, Regulation Z, or an equivalent rule, measure cumulative or fast repeat spend, or show that the supplied authority had not been revoked at authorization.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Use this receipt when a charge review needs the sequence of signed steps that led from a run's origin to its terminus. It checks that every declared input fingerprint equals the prior step's declared output fingerprint, with no unreceipted gap in the presented sequence. It also checks that recorded times do not run backward and recomputes the continuity finding rather than accepting it from the caller. That lets finance, risk, and legal inspect the run that was presented beside a charge. It is useful when an agent chose several steps after the original approval and the review needs an intact record of those steps.
What it does not do. It does not show that the first step caused the last step, that the last step caused a claimed effect, that any claimed effect occurred, or that anyone was harmed, and it never receives a description of that effect. It does not show that this was the only chain, rule out parallel or intervening causes, establish that the selected steps are those a court, regulator, or investigator would consider relevant, create legal liability, or provide an expert opinion on causation.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Every run above posts a verified request body from this domain to the open verify route and prints what came back. The example receipts are signed with published example keys, so verify reports key_trust example_registry. That is on purpose. Nothing on this page is a production issuance, a customer record, or an endorsement. Patent Pending.
Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.
Search the explorer for Ramp use case