Four products. One envelope.
Receipts, Inspect, Routing, and Settle are the four product surfaces of the Hive transaction envelope. They're built to work together and sold as a single platform, but each one covers a clear, separate job in your stack.
Hive Receipts
Every AI transaction ends with a portable receipt you can check offline. It's signed with Ed25519 by the requester, operator, and Hive, and anchored with SHA-256. It includes the request hash, response hash, origin fields, hardware attestation, and settlement reference.
Hive Inspect
Sealed-payload inspection. The operator encrypts with AES-256-GCM, and only named reviewers, like auditors, regulators, or your compliance team, can decrypt it with a ViewKey. Neither the operator nor Hive ever sees the plain data. Every time someone views it, that's a signed receipt too.
Hive Routing
Routing follows the rules you set. Origin, operator region, training region, hardware class, and settlement chain all get checked before any compute runs. Restricted regions get excluded at routing time. There's no silent fallback and no hidden routes.
Hive Settle
USDC on Base. It's issued by Circle, settles in under a second, and the settlement hash gets pinned right into the receipt. Hive never holds your funds. Permissioned chains work too if your policy requires it. The limit comes from your policy, not from the platform.
Hive-PQ is a proof tier, not a fifth product.
Hive-PQ doesn't replace the four product surfaces. It's a premium evidence profile you apply when a transaction needs long-retention, regulated, auditor-facing, or bank-grade proof. RubricMesh picks the right proof tier for each transaction (Standard, Pro, or Hive-PQ) and locks that choice into the receipt.
Standard for speed. PQ for permanence. Hive Standard proves everyday agent transactions. Hive Pro runs enterprise evidence rooms and dashboards. Hive-PQ keeps regulated AI transactions on record for long-term proof.
One SDK. One envelope. All four surfaces.
Receipts, Inspect, Routing, and Settle aren't four separate integrations. They're four sides of the same signed envelope. You wire up the envelope once, then turn surfaces on as your policy needs them.
Brief the right surface for your stack.
Tell us where you sit in the AI transaction. Issuer, operator, custodian, or supervisor, and we'll scope the right product surfaces for your setup.