forecast
Month-to-date spend projection for one project — burn rate, end-of-month estimate, and a confidence interval
forecast extrapolates a project's spend so far this month into an end-of-month figure, with a per-day burn rate and a 95 percent confidence interval. The period is always month-to-date; the command takes no options of its own.
$ solwyn --project proj_0123456789abcdef01234567 forecast
Metric Value
Project proj_0123456789abcdef01234567
Period 2026-09-01T00:00:00+00:00 - 2026-09-30T23:59:59.999999+00:00
Days 5 elapsed / 25 remaining
Current spend $12.500000
Forecast EOM $75.000000
Burn rate $2.500000 / day
95% CI $60.000000 - $90.000000
Insufficient data yes| Contract | |
|---|---|
| Auth | any (project key or JWT) |
| Exit codes | 0 success · 1 generic/API · 2 usage · 3 auth · 5 not found |
| JSON schema | solwyn.forecast.v1 |
Resolve the project with --project, SOLWYN_PROJECT_ID, or default_project in your config file; a missing project exits 2 before any credential is resolved.
Insufficient data is a first-class flag, not a reason to hide the numbers. Early in a month, or on a quiet project, the projection prints with yes here so you can judge how much to trust it.
JSON output
{"schema":"solwyn.forecast.v1","project_id":"proj_0123456789abcdef01234567","current_spend":12.5,"forecast_eom":75.0,"burn_rate_per_day":2.5,"ci_low":60.0,"ci_high":90.0,"period_start":"2026-09-01T00:00:00+00:00","period_end":"2026-09-30T23:59:59.999999+00:00","days_elapsed":5,"days_remaining":25,"insufficient_data":true}The same figures are available inline from status --forecast, and the Forecast-overrun alert rule fires on the projection. See Alerts & notifications.
Related
costs
Grouped cost breakdowns, paginated events, uncapped totals, raw and aggregated export, and the analytics subcommands — baseline, unit economics, drift, priced models, and simulation
overview
Calendar-month spend and request totals across every project in the account, with savings and the included-request quota