Getting started
Build, preview, and publish websites on unseal-space from your own agent or backend.
unseal-space turns a prompt into a deployed website. You describe what you want, an AI agent builds it in a sandbox, you watch it live, and you publish it to a domain.
This site documents the three ways to drive that from the outside.
Pick an integration
TypeScript SDK
@unseal-ai/unseal-space-sdk — a typed client for Node, Bun, Deno, or an edge runtime. The best
fit when you are writing code.
CLI
A standalone unseal-space binary with no runtime dependency, plus a ready-made skill file for
coding agents.
REST API
The raw HTTP surface, for any language, with a playground that sends real requests.
The shape of every integration
Whichever surface you pick, the model is the same.
- A project is one website. It owns a sandbox, a source history, an environment, and a preview URL.
- A message is one agent turn against a project. You send a prompt, the turn runs asynchronously, and it produces a new version. Only one turn runs per project at a time.
- A deployment publishes a version to production.
Every long-running operation is accept → wait: the mutation returns an id immediately, and you poll or stream until a terminal state. Nothing blocks on the server, and nothing is lost if your process dies — persist the id and resume.
Aborting a wait cancels your wait, never the remote work. The turn keeps running, the deployment keeps building. Always resume by id rather than re-issuing the mutation.
Next
Start with Authentication to create an API key, then follow the guide for your surface.