Token & cache savings

Articles

4 November 2026

How to reduce token usage without hurting output quality

Send each request only the earlier messages and search results its answer needs. Ask for shorter answers, and turn off the model's thinking step where a test allows it. Keep the start of every prompt identical: on our API, that repeated part is billed at a lower rate automatically.

13 October 2026

How to cut LLM API costs without hurting output quality

To cut LLM API costs without hurting output quality, measure cost per request and a quality score on your own evaluation set first, then apply the levers in order of risk: cache repeated prompt starts, cap output and reasoning tokens, move suitable tasks to a cheaper open model, and route simple requests to a small model, re-running the same evaluation after each change and keeping only what holds the score. If your LLM API bill is growing faster than your usage, this guide ranks the levers by quality risk and prices each one at Lyceum Serverless Inference list rates.

7 October 2026

Cutting Inference Spend by Routing Requests by Difficulty

Some requests may work well on a smaller model. Measure that share, include verification and escalation costs, and test quality before routing production traffic.

12 August 2026

Batch vs Real-Time Inference Pricing: When the Discount Wins

Major AI providers cut inference costs by 50 percent when teams route requests through asynchronous batch queues instead of real-time endpoints. Slashing spend requires isolating workloads that tolerate 24-hour turnaround times from those requiring interactive responses.

Your next workload starts here