This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Contextwaise
Send your LLM only the context it needs
Your LLM bill grows with context the model never needed: extra search results, raw tool output, old messages. Contextwaise trims it before each call. Prompt-cache safe, every removal logged, trimmed parts one call away. ~100 ms, any provider.
I'm Mohamed ABidi, an engineer. I build products on top of LLM APIs, and for a while my bills kept going up faster than my usage.
So I started looking at what we were actually sending. Most of it was context the model never needed: ten search results when two had the answer, raw tool output, logs, old messages. In agents it was worse, because every step resends everything from the steps before.
The clearest example: our demo agent ran a test suite, and the tool returned 7,209 tokens of passing tests and progress bars. The model needed the 2 failures, which were 156 tokens, and the rest was billed again on every turn after that.
I tried the usual fixes first: → Fewer search results: cheaper, but sometimes the answer got dropped → A cheaper model: cheaper, but quality dropped → Prompt caching: it helped, but it only discounts the repeated part. The noise is still there, just billed at a lower price. → Trimming by hand: it worked, but it broke the cache, and I had to rewrite it for every agent
Contextwaise is the tool I wanted instead. Before each call, it scores every item against the task and removes what the model doesn't need. It works on RAG results, tool output, web pages and memory.
The parts I cared most about getting right:
• Your prompt cache keeps hitting. Each item is decided once and replayed byte for byte, so trimming doesn't cancel out your caching savings. • Nothing is silently lost. Every removal is logged with its reason, and the model can call expand() to get trimmed parts back. • Easy to add. About 100 ms per call, any LLM provider, SDKs for TypeScript and Python. Wrap your model and tools, with no new model and no migration.
On our own demo agent, tools returned 52.6K tokens and the model read 9.1K. Cost went from ~$0.129 to $0.057. That's our test setup, so I'd love to see what it does on yours.
Contextwaise was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #84 on the daily leaderboard. Your LLM bill grows with context the model never needed: extra search results, raw tool output, old messages. Contextwaise trims it before each call. Prompt-cache safe, every removal logged, trimmed parts one call away. ~100 ms, any provider.
On the analytics side, Contextwaise competes within Developer Tools, Artificial Intelligence and Tech — topics that collectively have 1.6M followers on Product Hunt. The dashboard above tracks how Contextwaise performed against the three products that launched closest to it on the same day.
Who hunted Contextwaise?
Contextwaise was hunted by Mohamed Abidi. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Contextwaise including community comment highlights and product details, visit the product overview.
Hey Product Hunt 👋
I'm Mohamed ABidi, an engineer. I build products on top of LLM APIs, and for a while my bills kept going up faster than my usage.
So I started looking at what we were actually sending. Most of it was context the model never needed: ten search results when two had the answer, raw tool output, logs, old messages. In agents it was worse, because every step resends everything from the steps before.
The clearest example: our demo agent ran a test suite, and the tool returned 7,209 tokens of passing tests and progress bars. The model needed the 2 failures, which were 156 tokens, and the rest was billed again on every turn after that.
I tried the usual fixes first: → Fewer search results: cheaper, but sometimes the answer got dropped → A cheaper model: cheaper, but quality dropped → Prompt caching: it helped, but it only discounts the repeated part. The noise is still there, just billed at a lower price. → Trimming by hand: it worked, but it broke the cache, and I had to rewrite it for every agent
Contextwaise is the tool I wanted instead. Before each call, it scores every item against the task and removes what the model doesn't need. It works on RAG results, tool output, web pages and memory.
The parts I cared most about getting right:
• Your prompt cache keeps hitting. Each item is decided once and replayed byte for byte, so trimming doesn't cancel out your caching savings.
• Nothing is silently lost. Every removal is logged with its reason, and the model can call expand() to get trimmed parts back.
• Easy to add. About 100 ms per call, any LLM provider, SDKs for TypeScript and Python. Wrap your model and tools, with no new model and no migration.
On our own demo agent, tools returned 52.6K tokens and the model read 9.1K. Cost went from ~$0.129 to $0.057. That's our test setup, so I'd love to see what it does on yours.
Start free with 1M tokens at contextwaise.com.