Pay for context processing, with a share tied to realized dollar savings.
Zerix is the context middle layer for teams that already use frontier tiers, budget tiers, private endpoints, gateway accounts, or their own provider account. Compress what is safe. Preserve what cannot break.
Metered PAYG
Usage is recorded for Stripe metering; delivery can defer until Stripe configuration and customer records are present.
- PAYG only: no recurring plans or plan-gated engine behavior.
- Zerix charges a $0.25 base per 1M input tokens processed plus 25% of realized dollar savings. If realized dollar savings are $0, the savings share is $0.
- BYOK pass-through provider charges stay with the customer's LLM account.
- Public benchmark numbers stay pending attestation until the engine gate passes.
Meter Events
These are recorded by the live API path for metering.
A simple PAYG calculation
Fee = $0.25 per 1M input tokens processed + 25% × realized dollar savings. If realized dollar savings are $0, the savings share is $0.
This illustrates the locked fee unit in SSOT/12 §4; it is not a benchmark or savings promise.
Benchmark Claims
Savings, quality, latency, and ROI numbers are shown only from live request receipts or marked pending attestation. No public fixed benchmark numbers are published on this page.
Questions
Is Zerix a subscription product?
No. Zerix is PAYG. Processed-token usage and realized dollar savings create metered billing events; recurring plans are not part of the public model.
Do I need to move off frontier tiers, budget tiers, private endpoints, or gateway accounts?
No. Zerix prepares context before your existing model call. Keep your provider key in your own secret manager and call your downstream provider from your application.
What does Zerix return?
Zerix returns prepared context plus request metrics so your team can inspect token movement, quality telemetry, and billing inputs.
Where are public savings benchmarks?
They are pending attestation. The website should not publish fixed savings, quality, or latency claims until the engine team's verification gate passes.