API, CLI and MCP

Choice: One read API, /api/v1, with a personal token (Authorization: Bearer babul_pat_…) per person and company, read-only. Converters run where the code is wanted: the API hands out specs and tokens, and @babul/codegen writes files in the CLI, the MCP server and the web app alike. Over MCP a target with no converter is written by the agent, spending no Babul AI action. Packages: the API client, the CLI (babul), the MCP server, remote at babul.dev/mcp with OAuth 2.1 from Better Auth.

Why: the same request gives the same files everywhere.