Intelligence
FluxMeter Intelligence (heuristic)
Optional rule-based / heuristic APIs on top of metering data. Metering, attribution, budget controls, and export remain the primary product.
Last reviewed:
Methodology
Endpoint names checked against the engine Intelligence doc and claims.yml. Output quality depends on input completeness and configuration; operators must validate.
1. What Intelligence is
A set of HTTP APIs that read FluxMeter usage/cost rollups and apply rules/heuristics for root-cause decomposition, unit-economics views, scenario simulation, and report-shaped exports.
2. What it is not
- Not a trained ML consulting platform
- Not autonomous optimization or guaranteed business diagnosis
- Not “AI that tells you what to do next” as a proven prescription
- Not evidence of customer adoption or ROI
3. Inputs and dependency on metering data
Cost side comes from native ingest rollups. Unit-economics-style endpoints need revenue via OpenMeter overlay or POST /intelligence/revenue. Without revenue, responses may return unknown_revenue.
4. Currently available endpoints
Swipe horizontally to view all columns
| Endpoint | Status | Dependency | Notes |
|---|---|---|---|
| GET /intelligence/root-cause | Implemented | Depends on metering data | Spend delta decomposition (rules) |
| GET /intelligence/unit-economics | Implemented | Optional revenue overlay | Needs revenue overlay |
| POST /intelligence/simulate | Implemented | Depends on metering data | What-if scenarios |
| GET /intelligence/profitability | Implemented | Optional revenue overlay | Heuristic profitability view |
| GET /intelligence/forecast | Implemented | Depends on metering data | Linear forecast |
| GET /intelligence/report | Implemented | Depends on metering data | Export-oriented summary |
| GET /intelligence/summary | Implemented | Optional revenue overlay | Rule-based summary |
| GET /intelligence/pricing-recommendations | Heuristic | Depends on metering data | Rule suggestions — operator must validate |
| POST /intelligence/revenue/{id} | Implemented | Optional revenue overlay | Manual revenue write |
| POST /intelligence/import/openmeter | Optional dependency | Optional revenue overlay | OpenMeter revenue overlay |
| POST /intelligence/alerts/webhook | Implemented | Depends on metering data | Alert webhook |
| Langfuse / Helicone overlay | Planned | Planned | Backlog / planned |
5. Example output (explicitly illustrative)
Shape illustration — not measured customer evidence.
{"delta_pct":40.0,"summary":"…","contributors":[…]} // heuristic 6. Heuristic limitations
Decompositions and suggestions depend on rules and available dimensions; cost allocation may use heuristics. No guarantee of financial correctness or optimization gains.
7. Optional external revenue overlay
Revenue may come from OpenMeter import or manual POST. This is not a partnership endorsement and does not replace invoicing systems.
8. Operator validation responsibilities
Any suggestion, alert, or report must be validated by operators and finance processes before pricing or customer decisions.
9. Planned versus implemented
The table above distinguishes implemented, heuristic, optional-dependency, and planned items. Do not treat planned overlays as shipped capabilities.