How does condense actually shrink the bill?

Your agent re-sends the whole conversation to the model on every turn, so by mid-session you are paying again and again for text the model has already seen. On our own traffic 67.7% of the bill is re-reading old conversation, and only 0.2% is new text you just typed. condense shortens that history on its way to the model. Helene 1 handles the newest turn, dropping the parts that are not pulling their weight and passing the rest through word for word, fast enough that you will not notice it. Adeline 1 goes back over older work that is already finished and rewrites it to about a tenth of its length. What always survives: your instructions, what you asked for, and the answers you got back. Code, patches and error messages are never touched.

Will condense ruin my cache hit rate?

No. condense is built around the cache rather than in spite of it. We split each request into three parts. The oldest part is shortened once, then locked and never touched again, so the provider keeps serving it from cache cheaply for the rest of your session. The middle is the part still settling, which is due to be rewritten anyway. The newest part is this turn's text, which Helene trims before it is ever cached at all. Because the locked part only ever grows at the end, shortening what comes after it cannot spoil what is already cached. Our measured cache hit rate is 98.6%, and the published benchmark prices every run from real provider bills, so a broken cache would show up as a bigger bill rather than hide.

How much will I actually save?

It scales with how long your sessions get, because the saving comes from the history an agent re-sends every turn. Our published live run removed 37.3% of the bill on chains averaging ~179k tokens; sessions peaking past 800k save 66–72%. Dollar-weighted across all our own spend it comes to 66%. Chains under roughly 4k are too short to be worth compressing. The benchmark is public, so you can run it on your own sessions before you pay us anything.

How does condense compare to headroom, caveman or RTK?

We published a head-to-head against headroom: minmax-bench replays the same real session through both, reads back the real provider bill, and prices both the same way. condense removed 37.3% of the bill against headroom's best mode at 13.8%, close to three times as much. Compared only over the shorter sessions headroom managed, condense is at 28.0%, still about twice their best. The difference is built in: headroom's default setting keeps its cache clean but never touches the piled-up history that is most of the bill, while its more aggressive mode spoils the cache and ends at 1.8%. RTK, caveman and ponytail are not really competitors. They go after the model's replies and tool output, which is a different part of the bill, and they work alongside condense rather than replacing it.

What counts as a token saved?

Only the context we remove. If condense strips 4,000 tokens from a request before it leaves for Anthropic or OpenAI, that is 4,000 tokens saved: tokens the provider never saw and never billed you for. Whatever passes through untouched costs you nothing here.

Do I still pay Anthropic or OpenAI?

Yes. condense sits in front of your provider and uses your own API key, so the provider still bills you directly, just for far fewer tokens. That is where the saving lands. What you pay us for doing the compacting is either a flat monthly tier or a metered rate on the tokens we save.

Every tier is a weekly pool of tokens saved. Free gives you 25M a week. Starter is $5/month for 500M, Pro is $20/month for 2.5B, Max is $50/month for 10B. The pool refills every week, and when it is empty you drop to Condense Lite, which keeps compressing at about 20%. You lose some of the savings, never the service, and nothing extra is charged. Calling the API directly instead of subscribing costs 15% of what condense saves on your provider bill, so a request that saves nothing costs nothing. See the full pricing page for team plans and how to size a tier.

What happens when my weekly pool runs out?

Compression does not stop. You drop to Condense Lite, the same Helene 1 and Adeline 1 running under a cap, saving about 20% of a prompt until your pool refills at the start of the next week. Lite is a state of the plan you are already on, not a downgrade to a cheaper one: every tier lands on it when its pool empties and every tier goes back to full strength when the pool refills. Short sessions are identical either way, because the cap never binds on them. The longer a session runs, the more it wants to compress and the wider the gap gets, which is the whole argument for a bigger pool.

Does condense store my prompts or my provider key?

Your upstream provider key is never stored. Only a sha256 fingerprint reaches the usage ledger, enough to attribute requests without holding the secret. We never train on your data. Content is deleted on a 7-day window, and zero data retention is available on request. Application hosting is in AWS Europe (Spain); requests to api.us.condense.chat are processed in the US (us-east-1); external provider processing locations vary. Read the security page for the full posture.

November 3, 2026Release

See where your AI spend goes.

A new dashboard for AI spend, team budgets, and the devices behind the work.

By condense team

Demo data. Your spend and savings at a glance, with subscription usage and API costs shown separately.Open full size ↗

When the AI bill changes, you need to know why.

The latest condense release connects the overview to the work behind it. Follow spend to a team, model or session. Give people a budget they can work within. See which devices are running condense, and manage them in one place.

Spend visibility

From the bill to the work behind it.

Which team drove the increase? Which model? Which project? Break usage down by person, model, project or use case, then open the sessions behind it.

The Flow view connects those costs. My usage brings your own spend, cost drivers and savings together, with spend alerts and CSV exports when you need them.

Flow view connecting team spend to models, then to usage billed per token or covered by a subscription plan. — Demo data. Follow team spend through models to how the usage is paid for.Open full size ↗

Budgets

Give teams room. Keep spend in view.

Set provider-spend budgets for the organization, a team, a member or a model. See which limits need attention, and let members request more before they run out.

Monthly chargeback allocates spend to teams and cost centers. The organization limit is also visible on Home, with a direct link to Spend.

Budget table showing team, model, organization and member limits, health indicators, enforcement options and a pending raise request. — Demo data. Review budget health, raise requests and what happens at the limit.Open full size ↗

Enterprise devices

See the devices. Manage condense.

See installation status, usage, spend at API prices, savings and sessions in the Devices tab. Device filters carry through to analytics, sessions and inventory.

Switch condense on or off for a member or a device, or remove a device. Changes take effect at the next check-in and are recorded in the organization audit log.

Devices view expanded for a demo member, showing installed and removed devices, reported usage and member and device controls. — Demo data. Device status and controls, with usage through condense and usage while it was off shown separately.Open full size ↗

The details behind the rollout.

Controls for your API

Attribute API traffic to tenants, users, features and environments. Give service keys their own rate limits and spend caps, and send budget events to your systems through webhooks. Device controls are also available through the organization API.

Clear accounting. Defined retention.

Usage reported while condense is off is estimated at list prices and kept separate from budgets and chargeback.

Under zero data retention, an opaque device ID is kept for usage attribution. Session IDs, end-user attribution, tags and tool names are still dropped.

Available now

See the dashboard.
Plan your rollout.

Walk through spend visibility, team budgets and device controls with the condense team.

Book a call

Device management is part of Enterprise.