arkonrad
Looking for feedback on use cases and session controls (machine2machine).
On “thinking steps” and contamination: good point - naively persisting raw chain-of-thought tokens can degrade outputs. ARKLABS Stateful approach is not a blanket “store everything” policy.
And my criticism targets higher-level provider practices: things like response caching, aggressive prompt-matching / deduplication heuristics, or systems that return previously generated outputs when a new prompt is “similar enough.” Those high-level caches absolutely can produce the behaviour I described - a subtle prompt change that nevertheless gets routed to a cached reply.
The platform has been launched — we’re collecting data, but early results are very promising: we’re seeing linear complexity, lower latency, and ~80% input-token savings. At the same time we’d love to hear more feedback on whether this approach could be useful in real-world projects.
And about going against the grain, as you mentioned at the end… well — if startups didn’t think differently from everyone else, what would be the point of being a startup?
Show HN: Stateful LLM inference (no cost for input tokens, not prompt-caching)
Hi HN,I’ve been frustrated for a while with how LLM inference works in the cloud today. Every API call starts from scratch: you resend your entire prompt + conversation history, and you’re charged for every input token, even if the model has already “seen” that context before.This leads to two big problems:Performance & cost – constantly resending input tokens is wasteful.Quality loss –...
Show HN: Stateful AI API with OS Models
https://www.RogueFishMedia.com/
We just launched ARK Cloud API: OpenAI‑compatible, stateful AI inference service that keeps context across calls to slash token spend (0.01 USD / 1M input tokens), spins up in 10 s with Google SSO, runs fully on GDPR‑strong EU‑only infra, and gives 50 000 free credits at signup.Supports Stable Diffusion (cheapest rates), Llama 8 & 70B, embeddings, STT and more.PAYG, no logs, no data...