A privacy-first AI cost optimization platform that tracks every instrumented call across Claude, ChatGPT, Gemini, and Grok - without ever receiving a provider key, and without prompt content ever reaching Tokeven on the tracking path. Here's exactly how it works, end to end.
From API call to dashboard - four hops, no prompt content on the wire.
The wrapper (or the sidecar) reads response.usage after each call: token counts, model, latency, modality, and a local character count. Prompt content never reaches Tokeven.
Events flush to /ingest asynchronously (default: every 5s or 50 events). Authenticated by write-only ingest token.
Server recomputes cost_usd (cache-aware, authoritative). Idempotent on (org_id, event_id) - duplicates are silently dropped.
Three views query usage_events and usage_summaries. Sub-2-second load. Export to CSV/JSON on the Team plan.
Tokeven ships as a lightweight Python package. wrap() takes your existing Anthropic, OpenAI, Google or xAI client and returns an instrumented one - it dispatches on the client you hand it, so the same line works for all four. Grok has no SDK of its own: xAI serves the OpenAI protocol at api.x.ai, so it runs through the OpenAI SDK. No code changes to your prompts, no new dependencies in your hot path.
After each API call, the wrapper reads response.usage and captures: input/output tokens, cache read/write tokens, model name, latency, and a local character count of the prompt. It never sends the prompt content itself to Tokeven.
Cannot wrap the client - a different language, a tool you do not control? Run the self-hosted tokeven-proxy sidecar in your own environment and point the provider client at it instead. Those two paths - wrap() and the sidecar - are the only things that record usage. The MCP server is the pre-send advisor: it prices calls, it does not track them. Traffic that never passes through an instrumented path (the Workbench, a console, an un-instrumented app) will not appear in your dashboard. tokeven status tells you which paths are live on a machine.
Captures usage: token counts, model, latency and cost. Prompt content and your provider key never reach Tokeven.
The same 9,000-token system prompt is billed as fresh input on 755 Claude calls a week. Marking it cacheable bills the repeats at the 90%-off cache-read rate instead.
155 of your 370 claude-opus-4-8 calls this week were single-turn lookups. On the identical prompt, claude-sonnet-4-6 prices 40% lower.
3 gemini-3.1-pro workflows re-send full conversation history every turn. Summarising prior turns would cut fresh input tokens by ~35%.
Before you send, the advisor prices the call and scores cheaper alternatives across all four providers: what each would cost, and a confidence score for this kind of task. It runs entirely on your machine - as the MCP tool tokeven_estimate, as client.estimate(), or from the CLI. Then you choose. Tokeven never swaps a model on you and never downgrades a call silently; a suggestion you do not accept changes nothing about the request you make.
Prices behind those estimates are verified daily. Confidence scores are refreshed on a published schedule; the current refresh date is shown next to every score.
After the fact, the weekly digest is built from your actual usage patterns - specific optimizations with exact dollar amounts attached, drawn from calls your team already made (Team plan).
Three views, in the order the questions actually arrive: where is the money going, what should we change, and did the change work. Each loads in under 2 seconds.
Where your budget goes, by model, team, and session. Tabs for Overview, Cost Drivers, Models, Tokens, and Activity.
What to change next: recommendations, caching opportunities, and prompt efficiency - each with a dollar figure.
Every dollar saved, traced to the recommendation you accepted. Open book - this is the same math we bill from.
Around those three sit the pages you go to on purpose rather than daily: Team for per-person and per-team rollup, Weekly Analysis for the digest, Board Briefs for the monthly summary you forward, plus Export and API & Widgets.
The single biggest lever most teams have is caching: Save shows each engineer their own cache rate, what it is worth in dollars, and a weekly nudge to raise it - alongside per-call cost, model breakdowns, and team spend across all four providers.
See more comparisons across every model pair at /compare.
There is no phase list to wait out. Tokeven is one release - capture, advisor, dashboard, widgets, teardown tool, MCP server and integrations all landed together. Here is the whole surface area.
Free tier: one developer, the full dashboard, forever. Install in 2 minutes. Paid plans bill 10% of verified savings - if there is nothing to save, there is nothing to pay.
Start free