Original Summary

Once an AI bill stops being a rounding error, the first question is "which customers is that", and the provider dashboard has no concept of your tenants. Instrumenting every call site with logging is the obvious fix and nobody wants to do it. What I built is a proxy: swap the base URL, keep your own provider key, add a customer id header and a feature name header on each request. The proxy reads the usage block, prices it against a rate table, and the report groups by customer, feature or model, sorted by cost. The point is to turn "the bill doubled" into "this feature for these tenants" before the pricing conversation. How are others doing this? Per-seat flat pricing and hoping, usage-based, or something in between? Happy to share what I packaged if anyone wants to compare notes.   submitted by   /u/Imaginary-Storm3190 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/17 21:14:01