Changelog
0.3.0 — October 1, 2026
Public version is 0.3.0. Public title is Bellator Schedule Intelligence APIs.
Call the locked paths below. Old quality and schedule paths are one-hop 308 redirects, including async siblings. They are not the paths to document as current calls.
Samples on this site still use https://api.bellatorsi.com. That hostname is unchanged. This page does not retarget production.
Path table
| Retired path | Current path | Status |
|---|---|---|
POST /api/v1/schedule/validate |
POST /api/v1/analysis/validate |
308 |
POST /api/v1/schedule/cpm |
POST /api/v1/analysis/cpm |
308 |
POST /api/v1/schedule/cpm/async |
POST /api/v1/analysis/cpm/async |
308 |
POST /api/v1/forensics/resource-analysis |
POST /api/v1/analysis/resources |
308 |
POST /api/v1/forensics/resource-analysis/async |
POST /api/v1/analysis/resources/async |
308 |
POST /api/v1/forensics/logic-audit |
POST /api/v1/health/logic-audit |
308 |
POST /api/v1/forensics/logic-audit/async |
POST /api/v1/health/logic-audit/async |
308 |
POST /api/v1/forensics/progress-audit |
POST /api/v1/health/progress-audit |
308 |
POST /api/v1/forensics/progress-audit/async |
POST /api/v1/health/progress-audit/async |
308 |
POST /api/v1/forensics/dcma-14-point |
POST /api/v1/health/dcma-14-point |
308 |
POST /api/v1/forensics/dcma-14-point/async |
POST /api/v1/health/dcma-14-point/async |
308 |
POST /api/v1/forensics/dcma-decm |
POST /api/v1/health/dcma-decm |
308 |
POST /api/v1/forensics/dcma-decm/async |
POST /api/v1/health/dcma-decm/async |
308 |
POST /api/v1/forensics/planning-horizon |
POST /api/v1/health/planning-horizon |
308 |
POST /api/v1/forensics/planning-horizon/async |
POST /api/v1/health/planning-horizon/async |
308 |
POST /api/v1/forensics/schedule-risk-index |
POST /api/v1/health/schedule-risk-index |
308 |
POST /api/v1/forensics/schedule-risk-index/async |
POST /api/v1/health/schedule-risk-index/async |
308 |
POST /api/v1/simulation/risk-analysis |
POST /api/v1/simulation/monte-carlo |
308 |
Unchanged live paths:
POST /api/v1/health/scoreandPOST /api/v1/health/score/asyncPOST /api/v1/forensics/delay-analysisand/asyncPOST /api/v1/forensics/change-trackingand/asyncPOST /api/v1/forensics/baseline-compareand/asyncPOST /api/v1/forensics/as-planned-vs-as-builtand/async
410 composites
POST /api/v1/schedule/health and POST /api/v1/schedule/analyze return 410.
They are not aliases of POST /api/v1/health/score. Do not send new traffic to either path. Use POST /api/v1/health/score for the composite health score.
MCP
MCP is a caller surface, not a schedule-analysis family.
GET /mcp/toolslists the 14 family-prefixed names below. Simulation tools are not listed.POST /mcp/tools/{name}invokes one listed tool.{name}is the family-prefixed tool name, not an HTTP analysis path.
Unprefixed aliases are gone. Do not call simulation tools.
MCP tool names
| Family | Tools |
|---|---|
| Analysis | analysis_validate, analysis_cpm, analysis_resources |
| Health | health_score, health_logic_audit, health_progress_audit, health_dcma_14_point, health_dcma_decm, health_planning_horizon, health_schedule_risk_index |
| Forensics | forensics_delay_analysis, forensics_change_tracking, forensics_baseline_compare, forensics_as_planned_vs_as_built |
Not listed: simulation_what_if, simulation_monte_carlo, and unprefixed aliases such as logic_audit, schedule_validation, critical_path_method, resource_analysis, delay_analysis, baseline_compare, schedule_risk_analysis, dcma_14_point_assessment, schedule_health_check.
Missing logic vs dangling
- Missing logic is no predecessor and/or no successor (I05 / I06). That is DCMA 14-Point Check #1. It is not called open ends or dangling.
- Dangling start (I23): has predecessors, none are FS or SS, and no
actual_start. - Dangling finish (I24): has successors, none are FS or FF.
- Logic-audit keeps missing predecessor/successor as missing logic. I23 and I24 are separate dangling rules, not a rename of missing logic.
- Health score details distinguish missing logic (I05 / I06 / I07) from dangling start/finish (I23 / I24).
- DECM 06A204b Dangling Starts or Finishes uses I23 and I24, not I05 and I06.
Simulation is not implemented
POST /api/v1/simulation/what-if and POST /api/v1/simulation/monte-carlo are placeholders. They are not implemented and they are not MCP tools. The 308 from POST /api/v1/simulation/risk-analysis does not make Monte Carlo a supported call.