3 knowledge units
API-first custom service boundaryDeveloper custom code runs behind declared, schema-validated API endpoints so BuildWithHQ can bind custom logic into pages, workflows, AI, and external APIs without exposing platform core IP or direct unrestricted SQL.Four MCP surfacesBuildWithHQ’s MCP strategy separates Builder Account, Developer VM, SaaS Application, and End-Customer MCP surfaces while reusing common capability, permission, and audit primitives.Headless SaaS and scoped API clientsBuildWithHQ can act as a secured headless backend for external frontends, legacy systems, mobile apps, dashboards, and scripts through scoped API clients.