SiGR™ makes every AI inference call cryptographically accountable — a post-quantum signed receipt that proves exactly what the model saw, when, and which backend signed it. Verifiable by anyone. Forgeable by no one.
Four properties bound inside one signature. Alter any field and the proof breaks — no NDA, no shared secret, no trust required.
When an enterprise customer, an auditor, or a regulator asks "what did the model actually see, and is this the model we paid for?" — logs are not proof. Logs are editable. A signature is not.
The first platform that emits SiGRs makes the ones that don't look negligent by comparison.
A SiGR™ is a per-call header on your existing OpenAI-compatible API. You pay only for what you sign. Material-fragment signing (AFIR-S™) signs only the risk-bearing spans — tool calls, PII, decisions — and issues signed absence proofs for the rest, so you never pay to sign noise.
| Monthly volume | Base receipt | AFIR-S material fragment | SiGR surcharge on mid-model call |
|---|---|---|---|
| 0 – 10M | $0.00020 | $0.00040 | 27.8% |
| 10M – 1B | $0.00010 | $0.00020 | 13.9% |
| 1B – 10B | $0.00005 | $0.00010 | 6.9% |
| 10B+ | $0.00003 | $0.00006 | 4.2% |
Graduated tiers — each band priced at its own rate, like cloud egress. Platform pilot floor $2,500/mo. Material ratio assumed ~15% of calls in the model below; adjust to your traffic.
Drag to your monthly inference volume. This is the revenue line SiGR adds to your platform — and the cost line you bill through to enterprise customers who demand proof.
SiGR is not a feature you bolt on. It is the trust and accountability layer the platforms serving inference at scale will be forced to adopt to stay credible. Here's the revenue at stake as it spreads.
A drop-in on your existing OpenAI-compatible API. Customers opt in per call. Zero change to your inference path beyond the ~7ms signing step, which fails closed.
A regulated buyer chooses you over a hyperscaler specifically because you can prove what you served and what you charged. Trust becomes your differentiator, not your liability.
That win puts "can you emit verifiable receipts?" into every subsequent RFP. Your competitors now field a question they can't answer — and the category tips.
You're not the platform scrambling to add accountability after an incident. You're the one who defined what accountable inference looks like. Inevitable, and yours.
A 30-day pilot on one model family. We instrument your API edge, you emit live SiGRs on opt-in traffic, and we put a verifiable receipt in front of your most demanding enterprise prospect. If the bill, the provenance, and the timeline don't verify in front of them, you owe us nothing.