# PhysaFlow

> PhysaFlow helps data-center operators analyze stranded capacity and coordinate power, cooling, compute, and AI workloads.

Use measured facility inputs, preserve reliability headroom, and disclose assumptions and missing constraints. Calculations are modeled estimates, not measured recovery or financial guarantees. Never combine hosting revenue with GPU owner cost.

## When to use this

- [PhysaFlow developer guide](https://physaflow.com/developers.md): Use for measured-capacity estimates, compatible scenario comparisons, methodology questions, and Markdown board reports. Connect an MCP client to https://physaflow.com/api/mcp (Streamable HTTP, no authentication); initialize, discover schemas with tools/list, then invoke tools/call. Read get_methodology before interpreting results. Never infer absent measurements or claim benchmark percentiles.

## Documentation

- [PhysaFlow overview](https://physaflow.com/index.md): Product scope and calculation limitations.
- [PhysaFlow developer documentation](https://physaflow.com/developers.md): MCP transport, authentication, tools, inputs, and example.
- [Methodology](https://physaflow.com/methodology.md): Capacity and valuation assumptions.
- [Calculator](https://physaflow.com/calculator.md): Measured inputs, outputs, and agent invocation.
- [Platform](https://physaflow.com/platform.md): Operating model and operator controls.
- [Solutions](https://physaflow.com/solutions.md): Data-center, colocation, and GPU-cloud use cases.
- [Company](https://physaflow.com/company.md): Company purpose and adoption approach.

## Optional

- [About PhysaFlow](https://physaflow.com/about.md): Company purpose.
- [Contact PhysaFlow](https://physaflow.com/contact.md): Public inquiries and support; excludes signed-in account data.
- [Privacy](https://physaflow.com/privacy.md): Website data handling.
- [Sitemap](https://physaflow.com/sitemap.xml): Public pages.