The website builder for AI agents
A website builder for AI agents is one where the agent holds the verbs. It creates the site, writes the copy and publishes it — then keeps operating it: reading form submissions, drafting replies, updating content, checking analytics.
A human approves what goes live and what costs money.
Not the same thing as an AI website builder
The words are nearly identical and the products are not. One gives a person an assistant. The other gives an agent a website.
An AI website builder
The AI is a feature
- A person describes a site, the AI generates it
- The work stops when the person stops
- Operating it means opening a dashboard
- The output is a website
A website builder for AI agents
The agent is the operator
- An agent calls tools to build and change the site
- It keeps working between visits — on a schedule, or on request
- Operating it means asking, or letting the agent act
- The output is a website an agent can run
Why an agent needs different primitives
Anyone can generate a page now. The difference is everything that happens after that.
An API surface, not a canvas
A person needs a drag-and-drop editor. An agent needs verbs it can call. Sitelas exposes its whole surface as tools over MCP — create a site, patch a node, apply a palette, publish a page, read a submission — so building is a sequence of calls, not a cursor.
It reads state back, not just writes it
Generating a page is a one-way operation. Operating one is a loop: the agent has to see what changed. It can read form submissions, page analytics, version history and the rendered page itself — then act on what it finds.
It works with no chat window
The common door is a chat, but it isn't the requirement. An account API key gives an autonomous agent — Claude Code, a cron job, your own script — the same tool surface with no human in the loop and no conversation to belong to.
The guardrails stay human
The agent previews; a person publishes. Going live, paying for anything, and attaching a custom domain are never the agent's to take. Capability is the easy half — this is the half that makes handing over the keys reasonable.
Two ways an agent gets in
Both doors lead to the same tools.
Interactive — you, in a chat
Sitelas is in Claude’s connector directory and ChatGPT’s app directory, so adding it is one click. From then on the agent can act on your site inside the conversation you were already having.
Headless — an agent, with an API key
Generate an account API key and hand it to an autonomous agent. Same tools, no chat client, no person watching. Publishing, payment and custom domains still require you.
Read the docsGive an agent a website
Describe what you want and it builds you a real site — then keeps running it. You approve before anything goes live.