christalingx

5 ms·

1.
by christalingx 7mo ago
How it works under the hood (since HN will ask): No LLM call, no summarization — purely deterministic. Strips filler words ("basically", "essentially"), collapses verbose constructions ("in order to" → "to
2.
Show HN: I built a proxy that cuts LLM costs 40-60% – no AI involved(agentready.cloud)
2 points by christalingx 7mo ago|1 comments
3.
by christalingx 7mo ago
Hey HN, I built AgentReady — a compression API that sits between your code and your LLM. It deterministically strips filler words, redundant connectors, duplicate lines, and boilerplate from prompts before you send them. Same meaning, fewer
4.
Show HN: Compression API for LLM prompts (40-60% token savings, ~5ms overhead)(agentready.cloud)
2 points by christalingx 7mo ago|2 comments
5.
by christalingx 7mo ago
A new privacy-first API We redesigned our API — now the official version — to handle token compression with privacy at its core. We only require your AgentReady key. Your LLM API key stays yours — we never see it: --------------------------
6.
Show HN: I cut LLM API bill by 55% with a Python text compressor, no AI involved(agentready.cloud)
3 points by christalingx 7mo ago|1 comments
7.
by christalingx 7mo ago
I apologize for the confusion. The /v1/compress endpoint hasn’t been deployed yet. We’re pushing it to production asap. Following your suggestion, we’re also moving the compression step closer to the client side to minimize exposu
8.
by christalingx 7mo ago
Self-hosted version is on our roadmap. You’d run the compression engine yourself — we only validate your license key, nothing else touches our servers
9.
by christalingx 7mo ago
You’re absolutely right, and that’s a fair catch thank you so much. The example code contradicts what I said. The cleaner architecture — and what we should have shown — is a two-step approach where our API only handles compression, and your
10.
by christalingx 7mo ago
Do you need my OpenAI / Claude API keys? No. You only need our API key for the compression step. Your LLM keys and usage stay entirely in your own app — we never see them. We receive text, compress it, and return it. Your LLM (local, O
11.
by christalingx 7mo ago
Hi! You only need our API for the compression part — API keys and LLM usage are entirely managed by your own application. We don't have access to your SaaS, and we don't even know its name. We simply receive the text through our A
12.
by christalingx 7mo ago
Hi! You only need our API for the compression part — API keys and LLM usage are entirely managed by your own application. We don't have access to your SaaS, and we don't even know its name. We simply receive the text through our
13.
by christalingx 7mo ago
AgentReady is an OpenAI-compatible proxy. You swap your base_url, and every prompt gets compressed before hitting the LLM — 40-60% fewer tokens, same responses, same streaming. It uses a deterministic rule-based engine (not another LLM call
14.
Show HN: AgentReady – Drop-in proxy that cuts LLM token costs 40-60%(agentready.cloud)
8 points by christalingx 7mo ago|13 comments