Reference
API Reference
Organized by module family with representative endpoints, input expectations, equations, constants, and integration notes.
Overview
One physical model chain across operational software
Material properties and operating conditions are treated as upstream dependencies. Source models generate release rate and phase state; dispersion and fire/explosion models convert those outputs into consequence metrics; hazard-evaluation workflows then consume the same outputs for HAZOP, FMEA, and What-If studies. This makes the chain auditable and consistent across tools.
Modules
Documentation and product entry points
Training
Tutorials
Step-by-step examples for package users, API integrators, and browser-local users who want fast onboarding.
Application
Use Cases
Concrete patterns for pipeline leaks, toxic releases, siting screens, sign-triggered screening, and hazard-study support.
Repository
README and install notes
Use the README page for installation, packaging, Docker, MCP, and project-level details outside the API reference itself.
Highlights
Immediate platform capabilities
Comprehensive endpoint families
Materials, source terms, dispersion, fire, explosion, effect, prevention, relief, and hazard-evaluation modules are already exposed through the same API surface.
Transparent equations and constants
Equations, constants, and physical meaning are explicit in responses and docs. Constants can be overridden per request for sensitivity studies and what-if analysis.
Built for software integration
Use the same model contract in browser-local mode, Python notebooks, FastAPI services, Docker deployments, and MCP tools without rewriting calculation logic.