Docs / Choose a path
Build — choose a path
Pick how you call TokenSaver as a developer. All paths share the same governed pipeline and observability — only the client shape changes.
Start here if you write code or operate agent runtimes. Product/ops teams connecting market tools without code should use Connect — how to plug in.
tokensaver-cliOSS CLI — route Claude Code, Cursor & Codex; login, MCP, Flux IA.GitHub · PyPI · Hub page
tokensaver-egressOSS client HTTPS proxy (MITM) — govern traffic while keeping a provider subscription.GitHub · PyPI · Hub page
- LLM HTTP egress
- Client MITM egress
- MCP Trust Gateway
- A2A Gateway
| Path | Best for |
|---|---|
| CLI | Route Claude / Cursor / Codex in one command |
| LLM HTTP egress | Any OpenAI- or Anthropic-shaped client (drop-in base URL) |
| Client egress (MITM) | Keep provider subscription; local HTTPS proxy → Flux IA |
| Python SDK | Type-safe apps, RAG, chat sessions |
| Native REST | Full control over /api/v1 |
| MCP tools (A) | Platform tokensaver_* tools in an agent host |
| Trust Gateway (B) | Govern third-party MCP servers |
| A2A | Agent-to-agent JSON-RPC |
Scroll this tab for hub pages and deep dives (CLI, SDK, MCP, guides). API contracts live under API reference.