An extensive REST API over the whole model
The same connected model that runs Operating is open to your developers — people, skills, projects, allocations, time, budgets, invoices, and more. Full read and write, with pagination, filtering, and an OpenAPI spec. Integrate your stack, feed your reporting, or build on top.
The whole firm, one API
Full read and write access to projects, allocations, time, budgets, and invoices — the same structured model the product runs on.
Connect the rest of your stack
Off-the-shelf CRM connectors, plus an API that reaches everything else — your HR tool, finance platform, or reporting warehouse.
Built to be wrapped by AI
An OpenAPI spec and llms.txt index make the API easy to hand to an assistant and build agentic workflows against.
The whole firm, one API
No screen-scraping, no partial exports. The REST API reaches Operating's full structured model: projects and phases, positions and allocations, time entries, expenses, budgets, rate and cost cards, clients and invoices, with full read and write, and bulk operations where they matter.
Read and write people, projects, time, and financials
Bulk operations (e.g. time entries) and external identifiers for sync
Pagination, filtering, sorting, and a published OpenAPI spec
Connect the rest of your stack
Operating is built to fit into the tools you already run. Off-the-shelf connectors cover common CRMs; the REST API covers everything else — push data to your HR tool, pull it into your finance platform, or drive a reporting warehouse from one clean source.
Connect a CRM, HR tool, or finance platform via the API
Power external reporting from the same model the product uses
Keep Operating in step with the tools you already run
Built to be wrapped by AI
The API ships with an OpenAPI spec and an llms.txt index, so it's easy to hand to an assistant. Wrap it and build agentic workflows against Operating with Claude: the same clean model that powers the MCP server, reached programmatically.
OpenAPI spec and llms.txt made for AI tooling
Wrap the API to build agentic workflows with Claude
Same foundation as the MCP server, reached your way
Why open the whole model?
Screen-scraping and partial exports never give you the whole firm.
Operating already connects people, skills, projects, allocations, time, budgets, and invoices in one model. Rather than expose a thin slice of it, we opened the same structured model the product itself runs on — with full read and write, not just export.
Operating is built to sit inside your existing stack. The API exists so it can stay in step with the tools you already run, instead of becoming another island of data.
Off-the-shelf connectors cover common CRMs, and the REST API covers everything else: push data to your HR tool, pull it into your finance platform, or drive a reporting warehouse from one clean source. Pagination, filtering, sorting, and bulk operations come as standard.
We publish an OpenAPI spec and an llms.txt index because the API should be as easy to hand to an assistant as it is to a developer. Wrap it and build agentic workflows against Operating with Claude — the same clean foundation that powers the MCP server, reached your way.
Get the Operating Routine for resource planning
A weekly routine for staffing and capacity, written by people who ran it in their own firms. It gives your resource planning meeting a fixed agenda and a short list of numbers to check. Get the guide.
Thank you!
Get the Staffing Routine by clicking below.
Download guide
