Verticals · Inference platforms
Proof that disappears into your inference path.
Inference platforms need proof that does not slow the call or leak the prompt. Carnac™ sits invisibly in the request path, routes each call to the proof it warrants, and returns receipts that verify offline. Your customers' prompts stay on your side.
Where Hive fits
You already route calls across models and hardware. Carnac Gateway™ adds a proof layer in the same path: it proves the approved instruction arrived at the right model, unchanged, and countersigns the arrival. The plaintext prompt never leaves your boundary; Hive receives hashes, not content.
Privacy boundary
Prompts and outputs are hashed on your side. Only hashes and metadata cross to Hive. Receipts verify offline, so a customer or auditor never needs access to the prompt.
Integration path
Point traffic at the gateway, map your providers, set consequence thresholds, and return receipts to your customers. Hosted API today; in-VPC placement is customer-specific scoping.
Want the actual per-arrival cost before you scope this? The Gateway benchmark reports measured, reproducible throughput and p50/p95/p99 latency for the reference receipt core on a named machine, with a signed manifest you can verify yourself. It is a baseline to reproduce, not a production SLA or a comparison to any provider.
Use case mapped to Canon
| Canon primitive | What it proves here | Status |
|---|---|---|
| CarnacPrompt™ | Commits the assembled prompt window before the model runs. | Live core |
| AFIR | Signs routable inference fragments for agentic and long-document jobs. | Live core |
| SiGR | Turns any output into an independently verifiable receipt. | Live core |
| S2S | Binds a run to hardware evidence. Cryptographic core live; real-silicon integration required. | Live core, integration required |
Examples on this page show where Hive could fit inference platforms in general. They are not customers, partners, endorsements, or deployments.