Platform · Connect

Your portfolio data, wherever your tools are

Folio isn't a walled garden. A bearer-token JSON API exposes your portfolio data to the systems you already run, MCP servers hand it to AI agents, and calendar feeds put facilities events where your team plans its week.

Book Demo Open the console

folio.ai/docs/api OpenAPI

Integration API

GET /api/work-orders

POST /api/work-orders

GET /api/income-statement

GET /api/balance-sheet

GET /api/cash-flow

GET /api/reo

GET /api/reo/stakeholders

GET /api/work-orders 200 OK

List work orders across the portfolio — filter by building, property, status, category, or date range. Open orders first.

Bearer auth JSON Paginated OpenAPI documented

Three Surfaces

API for systems. MCP for agents. Feeds for calendars.

Each surface reads the same verified, source-linked data layer — the numbers your integrations see are the numbers your dashboard shows.

Integration API

Bearer-token JSON API

Work orders, financial statements, REO with stakeholder shares, and comparative records — served as clean JSON for your reporting stack or data warehouse.

GET /api/reo

MCP servers

Tools for AI agents

Facility and financial MCP servers let agents in Claude, Cursor, and other MCP clients work with your portfolio — manage work orders, pull financial reports, REO, and statement records.

list_work_orders

Calendar feeds

ICS where you plan

A personal, unguessable-token calendar feed puts maintenance and facility events into Outlook or Google Calendar — no logins, no exports.

facilities.ics

Coverage

What agents and integrations can reach

The integration API covers the records owners actually ask about — and every endpoint is documented in the interactive OpenAPI reference.

Resource What you get Access

Work orders List with filters, single record, create, update, delete APIMCP

Income statement Corporate income statement by property, year, and month APIMCP

Balance sheet Corporate balance sheet by property and year APIMCP

Cash flow Property cash-flow data APIMCP

REO + stakeholder shares REO report, stakeholders, and per-stakeholder share breakdowns APIMCP

Comparative records Raw comparative income statement rows by property and year APIMCP

OpenAPI reference Interactive documentation for every endpoint docs/api

The Console

One data layer, two ways in

The same verified records, shaped for the consumer — JSON for your systems, typed tools for your agents.

GET /api/reo?year=2026&month=5 Authorization: Bearer ••••••••

{
  "property": "West Loop Industrial",
  "period": "2026-05",
  "noi": 327400,
  "variance_pct": 8.4,
  "stakeholders": [
    { "name": "Harborview Trust", "share": 0.40, "noi_share": 130960 },
    { "name": "MK Family LP",     "share": 0.35, "noi_share": 114590 }
  ],
  "source": "May Operating Statement.pdf"
}

Auth & Control

Owner data, owner rules

Access is granted deliberately, scoped to what each consumer needs — and many owners run their production agents read-only.

Bearer tokens

Every integration API call authenticates with a bearer token you issue and can revoke — no shared logins, no scraping.

OAuth or API keys for remote agents

MCP servers running over HTTP support OAuth (Google, GitHub, Azure, or custom) or API-key authentication.

Local-first by default

MCP servers default to stdio transport — the agent runs beside your IDE or desktop client, and nothing listens on the network unless you choose HTTP mode.

See your portfolio in one trusted owner view.

Book Demo Portfolio Visibility Audit