Build on Tarleaks ERP

Everything the UI can do, the API can do — and everything the API can do, your AI tools can do over MCP.

The surface

• REST API per module. Every module exposes its full capability over JSON REST under /api/<module>/…, gated by the same licence, permissions and tenant isolation as the UI.
• MCP endpoint per module. Each module also serves the Model Context Protocol at /api/<module>/mcp — plus one aggregate MCP server — so Claude, IDEs and agent frameworks can read and act on your ERP data with per-tool permission checks. Kept 1:1 with each module's capabilities by construction.
• API tokens. Server-to-server access with scoped tokens; every call is attributed and audited.
• Events. Domain events (hires, payroll runs posted, certificates issued, tickets, campaign results) flow over a message bus — integrations subscribe instead of polling.
• Field-level audit. Every change records old → new values, so integrations are debuggable and compliance-provable.

Documentation access

Full API references ship inside the product per module, generated from the live routes of your own installation — so they always match the version you run. Public excerpts are available on request.