Skip to content

API Reference

This API reference is synchronized to the OpenAPI document served from /openapi.json and rendered with BellatorSI-specific context for standards, API categories, and operational behavior.

Use this page as your starting point, then drill into individual operation pages for parameter-level detail.

Current availability

  • Health is scored checks only: POST /api/v1/health/score, /logic-audit, /progress-audit, /dcma-14-point, /dcma-decm, /planning-horizon, /schedule-risk-index. Health score does not build the DAG and does not run CPM.
  • Analysis is POST /api/v1/analysis/validate, /cpm, and /resources.
  • Forensics is comparison only: POST /api/v1/forensics/delay-analysis, /change-tracking, /baseline-compare, /as-planned-vs-as-built.
  • Service liveness is GET /health and GET /api/v1/infrastructure/health. Those are not a health score.
  • POST /api/v1/schedule/health and POST /api/v1/schedule/analyze return 410. They are not aliases of /health/score.
  • Retired quality and schedule paths are 308 only. See Changelog. Do not document them as current calls.
  • Risk & Simulation is not implemented. Do not call simulation paths. Do not document /forensics/evm-analysis. Simulation tools are not MCP tools.
  • MCP: GET /mcp/tools lists 14 family-prefixed names. POST /mcp/tools/{name} invokes one listed tool.
  • The route-level catalog and operation detail pages are generated from the active API contract to minimize documentation drift.

Endpoint index

Production routes. Health is scored checks. Analysis is validate, CPM, and resources. Service is liveness, not a health score. Simulation is not implemented and is omitted. Allocate and level are not product routes. Full contract: /openapi.json

MethodPathNamePlanAsync
Health
post/api/v1/health/scoreHealth scoreFreeYes · /api/v1/health/score/async
post/api/v1/health/logic-auditLogic auditStarter+Yes · /api/v1/health/logic-audit/async
post/api/v1/health/progress-auditProgress auditStarter+Yes · /api/v1/health/progress-audit/async
post/api/v1/health/dcma-14-pointDCMA 14-PointStarter+Yes · /api/v1/health/dcma-14-point/async
post/api/v1/health/dcma-decmDCMA DECMStarter+Yes · /api/v1/health/dcma-decm/async
post/api/v1/health/planning-horizonPlanning horizonStarter+Yes · /api/v1/health/planning-horizon/async
post/api/v1/health/schedule-risk-indexSchedule risk indexStarter+Yes · /api/v1/health/schedule-risk-index/async
Analysis
post/api/v1/analysis/validateValidateFree—
post/api/v1/analysis/cpmCritical pathFreeYes · /api/v1/analysis/cpm/async
post/api/v1/analysis/resourcesResource analysisStarter+Yes · /api/v1/analysis/resources/async
Forensics
post/api/v1/forensics/delay-analysisDelay analysisStarter+Yes · /api/v1/forensics/delay-analysis/async
post/api/v1/forensics/change-trackingChange trackingStarter+Yes · /api/v1/forensics/change-tracking/async
post/api/v1/forensics/baseline-compareBaseline compareStarter+Yes · /api/v1/forensics/baseline-compare/async
post/api/v1/forensics/as-planned-vs-as-builtAs-planned vs as-builtStarter+Yes · /api/v1/forensics/as-planned-vs-as-built/async
Import
post/api/v1/import/xerP6 XERStarter+—
post/api/v1/import/mppMS ProjectStarter+—
Jobs / webhooks / account
get/api/v1/jobs/{job_id}Job statusAll—
delete/api/v1/jobs/{job_id}Delete jobAll—
post/api/v1/jobs/{job_id}/cancelCancel jobAll—
post/api/v1/webhooks/registerRegister webhookAll—
get/api/v1/webhooks/registrationWebhook registrationAll—
delete/api/v1/webhooks/registrationDelete registrationAll—
get/api/v1/webhooks/deliveries/{webhook_id}Webhook deliveryAll—
get/api/v1/account/tierAccount tierAll—
Service
get/healthService livenessPublic—
get/api/v1/infrastructure/healthInfrastructure livenessPublic—

Authentication and Required Headers

All protected routes require an API key header:

x-api-key: YOUR_API_KEY

Related docs:

  • Authentication workflow: /docs/authentication
  • Error behavior and retry guidance: /docs/errors

Request and Response Model

Track A endpoints are stateless. You send schedule data in each request and receive deterministic analysis results.

  • Single-schedule analysis: send one normalized schedule payload.
  • Comparison and forensic analysis: send all required datasets in the same request body.
  • No project persistence in Track A endpoints.

For payload structure and field semantics, use:

  • Task schema guide: /docs/task-schema-guide
  • Import normalization workflow: /docs/import-guide

Tiering, Limits, and Processing Mode

  • Synchronous threshold: up to 1,000 tasks.
  • Above sync threshold: async endpoints with job polling and optional webhook callbacks.
  • Access and task limits are tier-gated at runtime.

Use direct API calls for async workflows. The web playground is intentionally scoped for interactive testing.

Async Job Flow

For async-capable endpoints:

  1. Submit to the async route.
  2. Receive a job identifier.
  3. Poll job status or receive webhook callback on completion.
  4. Retrieve final result payload.

See /docs/webhooks for callback contracts and signature validation.

Compliance Context

Bellator references multiple schedule standards in deterministic analysis outputs, including:

  • DCMA 14-Point
  • GAO Schedule Assessment Guide
  • AACE recommended practices
  • Additional framework mappings documented in /docs/standards

OpenAPI Contract Access

  • Machine-readable contract: /openapi.json
  • Human-friendly index and operation navigation: this API reference section

When integrating SDK generation or internal tooling, treat /openapi.json as the source of truth.

Was this page helpful?

Your feedback helps us improve docs, reference pages, and Playground flows.

Topic: API Reference · Page: /docs/api-reference

TermsPrivacyContact

Schedule analysis guidance. Not legal advice. You remain responsible for contract and agency compliance.