Scale unrestricted private inference with ZAMA
Build a better unrestricted, private inference API than Venice through ZAMA-funded distribution and financially engineered compute. Deploy the roughly $50M ZAMA allocation over four years to win integrations, recurring demand and product quality. Use that demand to secure better compute terms, sell excess capacity and hedge price exposure.
Why unrestricted and private belong together
Security evaluation, trust-and-safety analysis, synthetic data, creative platforms and sensitive agent workflows need models that engage with difficult material while protecting the context they receive. Refusals interrupt the task; provider-visible prompts prevent customers from sending sensitive inputs. Abliteration and Venice already target these users. [S13][S09]
Measure unnecessary refusal rate, task completion, tool calling, latency and session cost. Verify the client-to-enclave connection, model identity, cache lifecycle and logs. Publish supported behavior and customer controls per model. [S11]
Buy licensed models and attested hardware against those workloads. Launch one or two endpoints with stable versions, predictable billing and reliable capacity.
Use ZAMA to buy distribution and retention
The $50M allocation averages $1.04M monthly over 48 months at its reference valuation. Confirm token release rights and conversion terms. Fund operating cash and futures collateral separately.
| Four-year allocation | What it buys | Release condition |
|---|---|---|
| 45% / $22.5M | Customer cashback and migration rewards | Incremental paid use and retention after taper |
| 30% / $15M | Agent, router and application integrations | Shipped integration and retained paid traffic |
| 15% / $7.5M | Capacity and supply relationships | Better delivered terms or availability |
| 10% / $5M | Model quality, verification and developer tooling | Accepted releases, evaluations and audits |
Tie partner and customer rewards to distinct milestones. Set dollar caps, token valuation rules and vesting. Keep fiat onboarding and optional token ownership. Track customer receipts, reward cost and retained spend by cohort; stop rewards that cannot repay their acquisition cost.
The flagship partnership Hermes private mode
Put a private mode toggle inside Hermes, backed by our verified inference route. Nous gains a privacy feature; we gain distribution inside an existing workflow. Use the Robot Ventures relationship for an introduction. Nous names Robot as an investor. [S35]
Hermes supports custom endpoints, auxiliary calls and provider fallbacks. Cover every model call with verified client integration and privacy-compatible routing. Stop the request if verification fails. Scope tool egress and local history explicitly. [S36][S37]
Pay a ZAMA integration grant against shipped milestones, then reward incremental retained usage. Give Nous commercial upside. Track enabled sessions, successful tasks, paid conversion and retention after credits. Use the resulting paid minimums to negotiate compute commitments.
Capture the compute commitment spread
Liquid Compute exposes commitment-versus-short-rental spreads and financing structures. Ornn supplies term curves; ICE offers an Ornn-indexed cash-settled GPU futures specification. [S31][S32][S33][S34]
Compare on-demand, reserved and financed-term quotes for the same TEE stack. Buy a base against partner minimums and shorter capacity for peaks. Negotiate prepayment, minimum draw, release windows and transfer rights together.
Sell excess capacity back to suppliers or through secondary buyers. Agree buyback prices, notice periods, placement fees and transfer rights at procurement. Retain the headroom needed for customer SLAs.
Use futures against the remaining exposure. Future floating purchases face rising rates; fixed-cost capacity with floating resale revenue faces falling rates. Match chip, quantity and tenor after customer commitments and physical sales. Include interest, index mismatch and collateral requirements in the cost comparison. [S33]
Negotiate supplier financing benefits into our rent, deposit or flexibility. Keep a cash reserve for collateral calls and service continuity.
OpenRouter supplies public demand
OpenRouter's October 28 routing change rewards realized price, speed and fewer failures. Use our procurement advantage to quote competitively while funding service headroom. Apply with excellent endpoints, full-session benchmarks, accurate cache reporting and Rand's introduction. [S01][S04]
Use ZAMA rewards for trials and integrations. Keep direct minimum-volume contracts as a demand base and router traffic as variable fill. Offer the direct verified SDK to customers who need protection from the router as well as the GPU operator. [S05]
Build the service Venice customers want
Venice has tokens, fiat API access and TEE/E2EE modes. Compete on execution. [S08][S09]
| Advantage | Product investment |
|---|---|
| Better compute terms, surplus recovery and hedging | Predictable prices, burst headroom and redundancy |
| ZAMA-funded integrations and migration | Native harness controls, setup help and switching credits |
| Focused model and verification budget | Fewer unnecessary refusals, stronger task success and stable versions |
| Simple API and billing | Plain invoices, optional tokens, explicit privacy routes and planned model changes |
The notes identify reliability, billing friction, token complexity, model churn and confusing privacy levels as Venice attack points. Compare customer workloads on failure rate, p95 latency, session invoices, task completion and privacy verification. Show the service and price customers receive after credits end.
Underwrite growth and compute together
Operating contribution = inference receipts + net capacity-sale proceeds − compute − funding − variable operations − incentives. Report hedge P&L separately. Count treasury-funded awards in acquisition cost. Track prepayment and collateral in cash requirements.
Stress token value, utilization, resale fill, rental prices and collateral calls together. Release funding in tranches against retained paid demand, operating contribution and liquidity.
The 90 day proof
| Window | Deliverable | Scale gate |
|---|---|---|
| Days 1–14 | Token/cash mandate, segment evals, Hermes proposal, partner baselines, TEE and exit quotes | Paid-pilot path and positive economics after rewards, funding and downside fill |
| Days 15–45 | Unrestricted/private API, harness integration, bounded compute book, milestone rewards | Strong task success and service; reconciled receipts, rewards and capacity recovery |
| Days 46–90 | Credit taper, retained cohorts, privacy review, recovery drill and portfolio stress | Retained demand, competitive service and positive operating contribution |
Rand owns treasury access, introductions and counterparties. Hire inference, confidential-systems, compute-structuring and product leads. Set the subsidiary's ownership, funding and token economics. [S21]