What it will do
Hand it a set of files and it deploys them — the same action the CLI and the MCP server already perform, made available as a plain HTTP call any system can make. No client to install, no assistant required, no dashboard in the loop.
Why it comes first
The deploy queue, the file guardrails, and the validation that keeps a bad upload from becoming a bad deploy all need to exist exactly once. Building them as an API means the CLI and the MCP server both call the same primitive instead of each reimplementing it, and anything built after them inherits it for free rather than needing its own copy of the same logic.
That's also why it isn't rushed. A REST endpoint is a public contract — once other systems are calling it, changing its shape gets expensive. The CLI and MCP server can absorb rough edges internally while it's still being worked out; a published API can't.
The plan for it
The same principle already governs the MCP server's tokens, and it carries over here rather than getting reconsidered from scratch.
A token authenticates to the API and can create, update and check the status of sites — the same actions available today, nothing wider.
No token, however it's scoped, will be able to see or change billing details. That boundary sits outside what any deploy credential can reach.
Removing a single site is in scope. Deleting the account underneath it is not — that stays a human action in the dashboard.
On the roadmap
Underpins the CLI and the MCP server — both already run today without it. No price and no endpoint documentation yet.
Not part of the static plan. Planned for after the core deploy paths, including this one, are solid.
Meanwhile
None of these are waiting on the API — they're already the real way sites go live, and they'll keep working exactly the same once it ships underneath them.
Connect a repository once. Every push after that republishes the site.
No repository required — just the files, dropped into the browser.
npx lemonade deploy, from wherever your files already are.
Connect the server once; your AI assistant deploys from the conversation.
Questions
No. Nothing about pricing is decided, and nothing on this page should be read as a preview of one.
There's no date to give. The CLI and the MCP server already cover the same publish action today; this becomes the shared primitive underneath both once it's ready, not a replacement for either.
Not directly — there's no endpoint to call yet. Git, a zip upload, the CLI and the MCP server are the ways to publish a site today, and none of them are waiting on this.
Join the list and we'll email you when it's documented and open — nothing before that. See what's included on the static hosting page, or check pricing.