Four products. One envelope.
Receipts, Inspect, Routing, and Settle are the four product surfaces of the Hive transaction envelope. They are integrated by design and sold as a single platform — but each maps to a clear, separable function in your stack.
Hive Receipts
Every AI transaction exits with a portable, offline-verifiable receipt. Ed25519-signed by requester, operator, and Hive. SHA-256 anchored. Includes request hash, response hash, provenance fields, hardware attestation, and settlement reference.
Hive Inspect
Sealed-payload inspection. AES-256-GCM at the operator, ViewKey-gated decryption for named reviewers — auditors, regulators, customer compliance — without exposing plaintext to operators or to Hive. Every disclosure is itself a signed receipt.
Hive Routing
Policy-driven jurisdictional routing. Origin, operator region, training region, hardware class, and settlement chain are evaluated before compute. Restricted geographies are excluded at routing time. No silent fallback. No hidden routes.
Hive Settle
USDC on Base. Circle-issued, sub-second finality, settlement hash pinned into the receipt. Hive does not custody funds. Permissioned chains supported as policy requires; the constraint is the policy, not the platform.
Hive-PQ is a proof tier, not a fifth product.
Hive-PQ is not a replacement for the four product surfaces. It is a premium evidence profile applied when a transaction requires long-retention, regulated, auditor-facing, or bank-grade proof posture. RubricMesh selects the proof tier per transaction — Standard, Pro, or Hive-PQ — and binds the answer into the receipt.
Standard for speed. PQ for permanence. Hive Standard proves ordinary agentic transactions. Hive Pro operationalizes enterprise evidence rooms and dashboards. Hive-PQ preserves regulated AI transactions for long-retention proof.
One SDK. One envelope. All four surfaces.
Receipts, Inspect, Routing, and Settle are not four integrations. They are four facets of the same signed envelope. You wire the envelope once and turn surfaces on as policy requires.
Brief the right surface for your stack.
Tell us where you sit in the AI transaction — issuer, operator, custodian, supervisor — and we will scope the right product surfaces for your environment.