<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Meter Demo on precomputing.com</title>
    <link>https://precomputing.com/tags/meter-demo/</link>
    <description>Recent content in Meter Demo on precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/meter-demo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI Usage Billing Case Study: A Month of Invoices That Match a Recount to the Billionth of a Dollar</title>
      <link>https://precomputing.com/ai-usage-billing-case-study-a-month-of-invoices-that-match-a-recount-to-the-billionth-of-a-dollar/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/ai-usage-billing-case-study-a-month-of-invoices-that-match-a-recount-to-the-billionth-of-a-dollar/</guid>
      <description>&lt;p&gt;An AI product that bills by the token has to count every request exactly once, even when the network does not cooperate. Clients retry, and a retry can arrive through a different gateway. A gateway that loses its link holds its reports and sends them hours later. A queue can stick at the end of the month, after the invoices are out. In the Meter demo the product&amp;rsquo;s gateways report every request to one meter, a compiled Precomputing policy inside SQLite, and the invoices are one SQL view over totals the meter keeps ready.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
