API, MCP, and OData: open Octowise without duplicating portfolio data
Integration keys, MCP gateway for AI assistants, OData for Power BI: connect existing tools instead of recreating a reporting silo.
Octowise Team
A portfolio system that only exposes its web UI will eventually recreate a reporting silo. Octowise opens the same data as the application: revocable integration keys, OData for Power BI, and an MCP gateway for AI agents, without duplicating the building repository.
The same data, beyond the screen
The API is documented and explored from the interface. Integration keys are revocable and carry a role scope: a Power Automate connector should not see invoices if the key lacks that right.
It is the same control model as for human users. There is no “reporting backdoor” that bypasses governance.
MCP: query the portfolio in natural language
The MCP gateway connects AI assistants to portfolio data, within the scope allowed by the key. An energy lead can ask for buildings late on OPERAT declaration or sources in error.
That does not replace dashboards. It speeds up one-off investigation, without extracting an Excel dump “for the AI” that will be stale the next day.
- AI assistants see the same data as the application.
- Scope limited by the integration key’s roles.
- Typical use: investigation, ad-hoc reporting, internal assistants.
OData for existing BI
Many organizations already have Power BI, a data warehouse, business models. OData feeds those tools without forcing a second building repository. Identifiers, surfaces, and org-chart attachments stay those of Octowise.
The classic trap is copying the portfolio into a parallel reporting tool that diverges within three months. OData feeds enterprise BI; operational dashboards stay inside Octowise.
Identity: Microsoft sign-in per organization
Each organization connects its Microsoft directory. Users sign in with the same account on web and mobile, without an extra Octowise password.
Opening the data without opening identity would create two access regimes. Microsoft sign-in, roles, and integration keys form the same governance system.