<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cost Optimization on API Coding</title>
    <link>https://apicoding.com/tags/cost-optimization/</link>
    <description>Recent content in Cost Optimization on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/cost-optimization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLM Response Caching Pays Off in CI, Evals and Agent Retries, Not in Chat</title>
      <link>https://apicoding.com/llm-response-caching-pays-off-in-ci-evals-and-agent-retries-not-in-chat/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/llm-response-caching-pays-off-in-ci-evals-and-agent-retries-not-in-chat/</guid>
      <description>&lt;p&gt;A repository has 300 integration tests that each send a prompt to a model. The suite runs on every push to every branch, then again in the merge queue. Most of those runs don&amp;rsquo;t touch a prompt (the diff was a stylesheet or a migration), so the model receives the same 300 requests it saw an hour earlier, writes roughly the same 300 answers, and the provider bills every one. Nobody chose that. It&amp;rsquo;s what happens when a test calls a live API.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
