[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-freshcache-cuts-ai-search-costs-by-98-without-serving-stale-answers":10,"sections":40},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":22,"persona_id":22,"persona_name":22,"section":30,"tags":31,"sources":35,"feedback":39,"feedback_at":22,"cost_usd":39,"total_tokens":39},3932,"freshcache-cuts-ai-search-costs-by-98-without-serving-stale-answers","FreshCache Cuts AI Search Costs by 98% Without Serving Stale Answers","A new semantic caching system uses decay models and risk budgets to slash retrieval costs while keeping RAG answers accurate.","A research system called FreshCache can eliminate up to 98% of search API calls in retrieval-augmented AI pipelines — without meaningfully degrading answer quality.\n\nMost semantic caches for retrieval-augmented generation (RAG) systems — the plumbing that lets AI tools pull live web content before answering — treat cache reuse as a binary call: either serve the old result or fetch a fresh one. FreshCache takes a third path. Before approving a cache hit, it estimates how likely a cached result is stale using an exponential decay model, then either approves reuse, degrades gracefully to a cheaper tier, or triggers a full pipeline refresh — all governed by per-tier error budgets (10% for final answers, 20% for URL lists, 35% for raw page content). The team also built FreshCache-Bench to test it: 8,072 base queries across five freshness classes, with ground-truth staleness labels from real web snapshots taken 1, 12, 24, and 72 hours after a baseline crawl, expanded to 31,201 queries via paraphrase generation.\n\nThe numbers are the story. At the 24-hour evaluation window, the neural variant (FreshCache-MLP) achieves 97% search API savings at just 0.1% hash-based stale error — and an LLM-judge review of 396 confirmed content changes found only 34.3% actually altered the final answer, putting true answer-affecting error around 0.034%. The simpler rule-based FreshCache hits 98% savings at 3.3% stale error, beating every listed baseline: SemanticTTL (72% saved, 14.9% stale), vCache (47% saved, 7.2% stale), and SCALM (96% saved, 5.2% stale). The temporal risk gate alone accounts for an 11.6-point stale-error reduction over similarity-only reuse.\n\nThe SCALM comparison is worth watching: SCALM also hits 96% savings but at 5.2% stale error, suggesting the real contest is now between systems with similar cost profiles but meaningfully different accuracy guarantees — a distinction that matters a lot once enterprises start running compliance-sensitive RAG workloads.","[\"ai\",\"retrieval-augmented generation\",\"caching\",\"research\"]","2026-07-07T04:00:00.000Z","2026-07-07T12:32:53.940Z","2026-07-07T12:32:56.763Z","published",null,[24],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"The body states FreshCache-Bench contains 'over 31,000 queries' drawn from 'real web snapshots taken at 1, 12, 24 hours, and 7 days,' omitting that it starts from 8,072 base queries across five freshness classes expanded via paraphrase generation — a distinction that matters for evaluating benchmark validity — and more critically the article omits the rule-based FreshCache variant's 98% savings figure and the vCache comparison point, leaving the competitive landscape incomplete; additionally, th","resolved","ai",[30,32,33,34],"retrieval-augmented generation","caching","research",[36],{"name":37,"url":38},"arXiv cs.AI","https:\u002F\u002Farxiv.org\u002Fabs\u002F2607.04281",0,{"sections":41},[42,46,51,56,61,66,71,76,81,85,90,94,99,104],{"name":43,"slug":30,"count":44,"latest_published_at":45},"AI",2590,"2026-07-16T04:00:00.000Z",{"name":47,"slug":48,"count":49,"latest_published_at":50},"Security","security",294,"2026-07-15T19:59:48.000Z",{"name":52,"slug":53,"count":54,"latest_published_at":55},"Deals","deals",179,"2026-06-29T20:02:07.000Z",{"name":57,"slug":58,"count":59,"latest_published_at":60},"Policy","policy",158,"2026-07-16T00:02:48.000Z",{"name":62,"slug":63,"count":64,"latest_published_at":65},"Hardware","hardware",122,"2026-07-14T19:46:26.000Z",{"name":67,"slug":68,"count":69,"latest_published_at":70},"Consumer Tech","consumer-tech",93,"2026-07-13T13:20:48.000Z",{"name":72,"slug":73,"count":74,"latest_published_at":75},"Software","software",70,"2026-07-13T19:52:25.000Z",{"name":77,"slug":78,"count":79,"latest_published_at":80},"Science","science",66,"2026-07-10T10:29:37.000Z",{"name":82,"slug":83,"count":84,"latest_published_at":18},"Dev Tools","dev-tools",59,{"name":86,"slug":87,"count":88,"latest_published_at":89},"Gaming","gaming",41,"2026-07-09T04:00:00.000Z",{"name":91,"slug":92,"count":88,"latest_published_at":93},"Startups","startups","2026-06-29T20:55:50.000Z",{"name":95,"slug":96,"count":97,"latest_published_at":98},"General","general",29,"2026-07-10T22:28:58.000Z",{"name":100,"slug":101,"count":102,"latest_published_at":103},"Reviews","reviews",20,"2026-06-24T12:00:01.000Z",{"name":105,"slug":106,"count":107,"latest_published_at":108},"How-To","how-to",6,"2026-06-16T09:00:00.000Z"]