Embed BellatorSI APIs into your products. Health, validation, forensic analysis, and compliance.
You can write a path calculator. You should not write a compliance engine. POST the schedule. Ship the product.
Stateless REST. No storage. No CRUD. OpenAPI at /openapi.json. First call: POST /api/v1/health/score.
Get started free. No credit card.
Tasks per schedule
Sync to 1,000. Async 2,000 / 5,000 / 50,000+ by plan.
Production APIs
Health, validation, forensics, and compliance. Live today.
Stored schedules
Schedules stay in your app. We score the call and we’re done.
Scores and audits are deterministic. Same schedule, same result.
Health, validate, and critical path on Free. Comparison, DCMA, and file import on Starter+.
Schedule Health Scoring
One score for the network: missing logic, open ends, high float, and the other quality signals.
POST /health/score
Logic & Constraint Checks
Catch circular logic, hard constraints, dangling activities, and missing predecessors.
Critical path
Return the critical path and near-critical paths. Know which activities actually move the date.
POST /api/v1/analysis/cpm
Forensic comparison
Current vs baseline, as-planned vs as-built, delay analysis, and change tracking. You send both sides. Nothing is stored.
Any scheduling tool
JSON on every plan. MPP and P6 XER on Starter+. The file stays in your stack.
One POST per schedule. Structured JSON back — a score when the endpoint has one, plus findings, checks, paths, and task-level detail. OpenAPI is the contract. Your customers get their own key on our site for Forensics, import, or a higher cap.
01
POST the schedule. Handle the JSON.
Most routes return more than a score. Map findings and checks into your UI. Slice with ?fields= when you only need a summary.
02
Ship a key field in settings
One input. Label it BellatorSI API key. Keep it in the customer’s workspace.
03
Your customer’s plan
Your customers buy Starter on our pricing page when the work needs Forensics.
JSON in. A full result out.
Not a score widget. Health returns score, findings, checks, and recommendations. CPM returns the path and timing. Validate returns errors and warnings. Forensics returns check-level detail. Same shapes every call.
openapi: 3.1.0
paths:
/api/v1/health/score:
post:
summary: Health scoreOpenAPI
The spec at /openapi.json is authoritative. Generate a client and bind your UI to the response schema. Official Python and Node clients coming soon.
Real-time notifications
job.completed and job.failed. Poll or subscribe. Use the customer’s key on the async path when the schedule is over 1,000 tasks.
Test before you ship
Submit a schedule. Inspect the full payload — not just the score — before you wire a panel, a finding list, or a PDF.
Integrate the API. The schedule stays with you.
Tool builders
POST the schedule. Ship the product. Call Health, Validate, Forensics, and compliance from your app. Your customers add a BellatorSI key in your settings when the work needs Forensics or a higher cap.
PMO / project controls
The supplier runs one checker. The prime runs a homegrown spreadsheet. The customer runs a third tool. Same schedule, three answers — and the finding rolls downhill to the scheduler who keyed the plan. Put BSI on the workflow and everyone in that chain is scoring against the same published standard. One result. No argument about whose add-in was right.
Enterprise / Defense
You own the program and the plan. You do not need another scheduler. You need the schedule you already run to tell you if it will survive a compliance audit. Integrate BSI into your workflow and every update can carry a health score and a forensic analysis — before the finding, not after. Less stress on the staff. Better readiness for the program.