Writing
Practical notes on metering, architecture, and budget controls. Intelligence and market-map pieces stay secondary.
Budgets Integrations Architecture Intelligence Metering
Featured
2026-07-04 · Budgets
A runaway agent loop can consume a prepaid balance before a periodic billing job notices. An illustrative scenario on why pre-request controls matter.
Read article →2026-07-11 · Integrations
Keep Stripe, Metronome, or Orb as the invoice system of record while FluxMeter owns pre-request enforcement — plus hierarchy reserve, per-key budgets, and metadata dims in v2.8.0 / SDK 1.5.0.
2026-07-11 · Architecture
OpenMeter focuses on usage → invoice. FluxMeter focuses on customer-level metering and optional hot-path checks, plus heuristic Intelligence APIs on the same rollups.
2026-07-11 · Intelligence
Why AI companies need Layer 4 intelligence — root cause, unit economics, simulation — and how FluxMeter maps against observability and billing tools.
2026-07-11 · Intelligence
Compute per-customer revenue vs LLM cost, margin, and loss alerts from Redis rollups — no ClickHouse or BI warehouse required.
2026-07-06 · Budgets
Ship pre-request enforcement with Python wrap(OpenAI()), hard-cap agent runs, and Lite BUDGET_WARN webhooks — FluxMeter v2.7.0 and SDK 1.4.0.
2026-07-05 · Metering
Expose monthly, daily, session, and agent span usage to your customers with GET APIs — no Snowflake or BigQuery required.
2026-07-04 · Budgets
Compare pre-request budget checks and post-hoc usage analytics for LLM products. When to block before the call vs reconcile after.