<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI on RollupDB.com</title>
    <link>https://rollupdb.com/tags/ai/</link>
    <description>Recent content in AI on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracking AI Model Cost and Token Use per Feature With RollupDB</title>
      <link>https://rollupdb.com/tracking-ai-model-cost-and-token-use-per-feature-with-rollupdb/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/tracking-ai-model-cost-and-token-use-per-feature-with-rollupdb/</guid>
      <description>&lt;p&gt;An app calls two language models, a large one and a small one, from three features: a support chat, document summaries and search. Every call has a token count and a price. Finance wants the monthly bill split by feature. Engineering wants to know which feature sends the longest prompts, and whether moving support chat to the small model last quarter actually saved money.&lt;/p&gt;&#xA;&lt;p&gt;The provider&amp;rsquo;s dashboard shows the bill, not your features. Logging every call answers everything, and in a year it&amp;rsquo;s millions of rows, most holding prompt text you&amp;rsquo;d rather not keep at all. What the questions need is sums and counts per model and feature over time, plus the shape of the token counts. RollupDB keeps that and lets the calls go.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
