The Token Saver Program
What Elis Token Saver is, how it saves your AI host tokens, which wallet it bills, and where to review every plan it ran.
Elis Token Saver is a remote MCP server you connect to an AI coding host — Claude, Claude Code, ChatGPT, or Codex. Instead of letting the host answer every prompt on its most expensive frontier model, Token Saver breaks the goal into right-sized tasks and tells the host which size of model each task actually needs.
Understand where the savings come from
A typical coding session mixes trivial work (rename a variable, read a file) with genuinely hard work (design a migration). Hosts run all of it on one frontier model. Token Saver returns a task graph where each task carries a recommended size — nano, small, or frontier — so the host can spawn cheap subagents for the cheap work.
The saving is measured as a counterfactual: what the same work would have cost on a frontier model, minus what it actually cost. That number is what you see on every savings surface in the product.
Connect a host
Connection is a one-time step per host. Developers should follow Token Saver MCP — Six Harnesses for the exact connector URLs and commands; the short version is a single Claude Code command:
claude mcp add --transport http elis-token-saver https://api.tryelisai.com/api/mcp/claude
Production requires OAuth sign-in, so the plan runs under your linked Elis account rather than anonymously.
Choose the billing scope during consent
The OAuth consent screen shows an organization picker. This choice decides which wallet the run bills and who can see it:
- Personal (default) — charges your personal wallet, drawing first on that wallet's own daily free grant. Only you see the runs.
- An organization — charges the org wallet, drawing first on the org wallet's own pooled daily free grant, and makes the runs visible to org admins on the organization's observability page.
Pick deliberately. Work you do for a client or employer belongs on their org so the spend and the audit trail land in the right place.
Run every task with /elis
Setup is a one-time job: your developer (or you) asks the host to set up Elis Token Saver host instructions, which installs a shortcut called /elis — see Token Saver MCP — Six Harnesses for that one step.
From then on, type this before each task, then describe what you want done:
/elis
That word is what turns the savings on. It starts the plan, runs each task at the tier Elis selected for it, and finishes the plan at the end. Installing it once and then working the way you always have gives the savings back — the host quietly goes back to answering everything on its most expensive model. Letting the plan reach the end matters too: an unfinished plan is not remembered, so a similar job later has to be worked out from scratch instead of replayed.
Review your savings
Personal runs roll up on the Show Your Savings page:
/savings
Organization runs appear under Organization → Observability → Token Saver, listing every plan attributed to the org — its tasks, the settled estimated tokens saved, and the Elis fee. Admins can filter by member to see who is driving the spend.
Handle a paused plan
If a plan returns payment_method_required, the account you selected at consent has exhausted its wallet's daily free grant and has no way to pay overage. Attach a payment method, then re-run the same request:
https://app.tryelisai.com/billing
For an organization scope, an org admin attaches the payment method on the organization's billing surface — a personal card will not unblock an org-scoped plan.
Decide what gets remembered
A plan that finishes successfully is stored privately in your scope as a proven chain, so a similar future goal replays the known-good task sequence instead of re-planning. Sharing those chains with other participants is a separate, off-by-default opt-in — see Community Sharing.