Usage, plus a little
orchestration.
The proposal is simple: applicable usage plus a 5% orchestration fee, without a monthly subscription. Build your model orchestration on theo’s built-in MCIR memory layer.
Proposed pricing · billing alignment pending. The live billing documentation and your account terms remain the source of truth.
+ 5%
A simple worked example.
Not a quote for your workload.
01do the arithmetic
Put a number on paper.
This calculator only demonstrates the proposed fee. It does not measure a prompt, estimate model usage, or contact the billing system.
What if my usage were…
Up to $100,000,000.00. Commas group thousands; a period separates cents.
Or try an example amount
applicable usage + 5% proposed fee = illustrative total
Browser-only arithmetic. Nothing is stored or sent.
The fee is rounded to the nearest cent in this illustration. This does not model taxes, account terms, or individual capability rates.
5%
for bringing the pieces together.- example applicable usage
- $100.00
- 5% proposed orchestration fee
- $5.00
- illustrative total
- $105.00
USD example. Not a live quote.
02know what you’re looking at
A clear proposal. Not a hidden promise.
- 01
Usage is the starting point.
The example starts with an amount of applicable usage. Find actual capability rates, metering, and account details in the current billing documentation before estimating your workload. - 02
Orchestration is the addition.
The proposed 5% fee is calculated on that amount. For $100 of applicable usage, the example adds $5 and arrives at $105. - 03
No subscription in the proposal.
This direction avoids a monthly subscription. It is not a statement that the current billing system has already adopted that structure. - 04
Controls still need configuration.
Pricing does not activate policies, configure routing, or approve a sensitive deployment. Review your keys, permitted tools, spending controls, and data responsibilities separately.
03the small print, in plain language
A few fair questions.
Is this the live price today?
No. This is a proposed pricing direction and billing alignment is pending. Consult the current billing documentation and your account terms before estimating production spend.
What would $100 of usage look like?
In this illustration, $100 of applicable usage plus the proposed $5 orchestration fee totals $105. It is arithmetic, not a quote for a particular model, tool, or workload.
Can this tell me what my prompts will cost?
No. The calculator does not inspect prompts or predict tokens, tool use, retries, or workload size. Start with a small, non-sensitive test in the real app and inspect its actual usage information.
What does built-in memory mean for this estimate?
MCIR is part of theo’s context architecture, not a separate integration you need to build. This calculator still only illustrates the proposed fee; it does not quote memory storage, retention, or workload costs. Use current billing documentation and account terms for those details.
Are policies or healthcare approvals included?
A pricing model is not a policy configuration or a deployment approval. Gateway Guardrails are opt-in and must be bound appropriately. Healthcare work still requires review of the complete data flow, agreements, tools, and application workflow.
Can I try the workbench without creating an account?
Yes. The educational workbench runs in this browser with synthetic sources and mock tools. The real API and production playground have their own authentication and usage requirements.
Start with understanding, not a bill.
Build a sample workflow and inspect its decisions before connecting a real application.