Hive creates signed receipts for AI requests, agent actions and payments. Free tier, then $99/mo plus per-receipt usage. See features and limits.
Researched and fact-checked by Bartu Cavusoglu · Updated October 26, 2026
Hive builds tools that create signed records for selected automated actions. When a workflow is integrated with the relevant Hive component, an AI request, agent run, payment or signed document can leave a separate receipt that an authorized party can check later.
The receipt sits beside the answer or action and never inside it, so the original output is unchanged. Hive is careful about what a receipt proves. A signature checks the signed statement, not the accuracy of an answer or which model actually ran.
The company is listed as Hive Civilization, a Wyoming corporation with an operating address in Walnut Creek, California, established in 2026. The site says these details are declared and not independently verified.
The platform page describes a signed envelope that a transaction passes through: request authored, policy applied, route resolved, receipt issued and settlement closed. Each step writes fields into the receipt, and the site says that if a step cannot be signed, the call does not go through. This is labeled as a proposed transaction flow.
On the homepage, the Carnac family splits the work into roles. CarnacPrompt signs the original request. Carnac applies a signed policy to decide how much proof is needed and routes the request as routine, review, hold or abstain. Carnac Gateway compares an arriving instruction with an approved version and can countersign the arrival.
Receipts use Ed25519 signatures and SHA-256 anchoring. Offline checks need a supported receipt, verifier resources and trusted keys.
Hive Recorder is aimed at AI agents. Keys sit outside the agent, each tool call is witnessed before it runs, and public timestamps fix the time. The homepage says anyone can ask the witness later and that it runs today in real Claude Code sessions.
Hive Radar sends synthetic requests through selected provider paths and signs the records it captures. Hive notes that these checks cover the tested paths, not a provider's entire service, and that providers do not sign the model output shown.
The platform also offers requester-declared routing policy enforced before compute, sealed payloads using AES-256-GCM, and a ViewKey grant flow for named reviewers. Sealing and signed manifests are listed as live, while the ViewKey grant flow is a pilot shipping under the regulated tier.
Hive builds tools that create signed records, or receipts, for selected automated actions such as AI requests, agent runs and payments. Teams and authorized reviewers can inspect the fields an integration captures.
The pricing page lists a Free tier at $0, and Builder at $99/mo and Operator at $299/mo, each plus per-receipt usage. Per-receipt rates run from $0.00007 to $0.0018 depending on signature tier and volume. Enterprise terms are quoted after workflow mapping.
Yes. The Free tier allows 100 receipts per IP per day with no signup, and the site also says you can start free with 1,000 receipts and 30 days, no card.
Yes, with conditions. Offline checks need a supported receipt, verifier resources and trusted keys. Local checking is not metered.
No. The site states a signature checks the signed statement, not the answer's accuracy or which model actually ran.
The sources name Claude Code, where Hive Recorder runs, and USDC on Base as an optional payment and settlement rail. Other integration details depend on the endpoint.
It suits compliance, security and operations teams, and builders of agent products, who need verifiable records of selected automated actions. Regulated firms are a stated focus.
The company page lists Hive Civilization as a Wyoming corporation with its operating address in Walnut Creek, California, established in 2026. The site says these details are declared and not independently verified.