Atelier201 websiteJoin the waitlist
WorkspaceCommit the workspace
sites

Commit the workspace

Saves every uncommitted change of the workspace as ONE history entry, through the commit guard (no secrets, no .env, no server code, valid JSON). Nothing to commit: changed is false.

POST/v1/sites/{site_id}/workspace:commit

Requires sites:write. Costs no credits. The path ends in /workspace:commit. Changes the draft only. Visitors see nothing until you publish.

All the workspace’s uncommitted changes become one history entry, whatever the number of files. summary is required, at most 500 characters: one sentence on what the change does, which is what people read in the history.

The same commit guard applies as for every other change. A secret, a .env file, server code or invalid JSON is refused with 400 and the reason, and nothing is saved: fix the file in the workspace and commit again. Every finding is listed at once, with its file and line.

A file the project’s .gitignore lists (a .env.local, a key file) is never part of a commit, so it is never refused either: it is left out. When such a file looks like a secret, the answer names it in not_committed with a warning: it was not saved, never reaches the site, and is gone when the workspace restarts.

With nothing uncommitted, the call succeeds with changed: false and no new entry. Otherwise revision is the new entry, parent the one before it and changes the paths it touched. If another change landed on the draft in the meantime, your edits are carried over and note says so.

Next, start a build to see it in a preview.

Authorizations

Authorizationbearerin headerrequired

Path parameters

site_idstringrequired

The site's id, or its slug (the address before .atelier201.page).

Body

application/jsonrequired
summarystringrequiredlength: 1–500 chars

What the change does, in a sentence: the history entry people read.

Response

application/json

Commit the workspace's changes

dataobjectrequired
request_idstringrequired

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Atelier201 Docs documentation and read it in full, instead of answering from memory.

https://atelier201.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://atelier201.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.