Cost Attribution & Forecasting

What it does

Attribution groups synced spend by the provider’s native project or workspace when your key has org-level access. OpenAI projects and Anthropic workspaces map into Fluxtab’s project fields. OpenRouter usage is not attributed to projects.

Forecasting shows two paces next to month-to-date spend for the current calendar cycle:

• A recent pace (last 7 days of usage, projected to cycle end — shown once you have at least 3 days of data)
• A flat month-to-date pace for the same cycle

Both are labeled in the product as an estimate, not a guarantee. They extrapolate this calendar month only and are separate from whatever date-range total you are viewing on the chart.

Why use it

Attribution answers “which project burned the money?” Forecasting answers “if this pace continues, where does the cycle land?” Together they support threshold alerts and the CI spend gate without implying Fluxtab can hard-stop provider traffic.

Setup

1. Connect a provider key with org-level access under Settings → Connections (see Providers).
2. Sync usage. If the key cannot group by project/workspace, totals still appear; project breakdowns stay empty until the provider side is split or the key is upgraded.
3. On the dashboard, read MTD spend and the forecast block. Wait until you have at least three days of data before expecting the recent-pace estimate.
4. Set a monthly threshold under Settings → Alerts so estimates are paired with real warnings — forecasts alone do not page anyone.

OpenRouter history remains limited to the last 30 UTC days even on higher plans; forecasts that depend on recent days still work inside that window.