Running a model costs what you send it and what it takes to hold and execute it. The industry has spent a decade on the first. R-Sym works on both.
Prompt caching, shorter prompts, cheaper models, better retrieval — every one of these reduces what reaches the model. None of them change what the model costs to run once it gets there.
Tokens, context, retrieval. Understood, competitive, and where nearly all the effort has gone.
Memory residency, how weights reach the device, and what has to execute at all. Fixed cost, treated as a constant.
Reduction and context are deployed and billing today. Trust is what makes both auditable. Runtime is the second half.
Reduction cuts what a provider bills for on a call you were already making. The model receives what it needs to answer correctly, and what it received can be reconstructed exactly — reduction is recoverable, not lossy.
Because the effect lands on the provider's own invoice, you never have to accept our measurement. The number is theirs.
Reduction →Three things that are usually treated separately: fitting more working context into the same window, keeping that context alive across calls and restarts, and addressing one context surface from more than one provider.
Corpus retrieval sits here too — reasoning across a large local corpus without standing up a vector pipeline to do it.
Context →The same approach applied a layer down: what stays resident in device memory, how weights get there, and what actually has to execute to produce a token.
In development. We are not publishing figures on this work yet.
Runtime →Every dispatch produces a signed receipt. Reduction claims, billing, and the reconstruction check are all recorded against a hash chain you can verify independently.
An efficiency claim you cannot audit is a marketing number. This is the part that makes the rest of it a contract.
Trust →Nothing here is a separate integration. A single dispatch passes through whichever surfaces your account has enabled.
Your existing call, pointed at the endpoint. Your provider key, your provider account.
Billed input is cut. Context is resolved from whatever is already held.
The provider is called normally and bills you normally, for less.
The result returns with a signed record of what happened and what it saved.
Bring your own provider key. Billing stays with your provider. The difference lands on their invoice.