Atelier201 websiteJoin the waitlist
REST APIAPI overview
REST API

API overview

What the REST API does, where it lives, and how to create, change and publish a site with it.

The API is at https://api.atelier201.com/v1. It can do everything the app can, and the CLI and the MCP server use the same contract.

Your first call

Terminal
curl https://api.atelier201.com/v1/account \
  -H "Authorization: Bearer $ATELIER201_API_KEY"

Call /v1/account first. One request tells you the workspace, the plan and precisely which scopes the credential you hold was granted. Discovering those one 403 at a time is the slow way.

From nothing to a live site

Each step is one call. Only the last one changes what visitors see.

  1. Create a site. It starts from the Atelier201 starter and builds once.
  2. Read the content model, then change texts and entries with Create or update an entry and Change one field.
  3. Build the site and poll the build until it is ready.
  4. Share a preview and show it to the owner.
  5. Review, then publish after the owner approves.

The concepts behind each step are in How a site goes live.

Costs

Editing, building, previewing and publishing are part of the site’s plan and spend no credits. One endpoint does: making an image or video with AI, at a fixed price you get first for free, behind its own media:generate permission. See Plans and credits.

What it does not do

It is not a streaming API and it does not hold a connection open. Starting a build returns at once with a queued build, and you poll for the result. A build survives your client disconnecting.

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.