Atelier201 websiteJoin the waitlist
SitesCreate a site
sites

Create a site

Creates a site from the Atelier201 starter (an Astro project with a content model), at .atelier201.page, and starts its first build. Nothing is published: call publishSite when the preview looks right. A workspace holds 10 drafts (25 once it has paid for anything); paid sites are not limited. Only a site on the Site plan can be published: a draft is shared through preview links.

POST/v1/sites

Requires sites:write. Costs no credits. Nothing is published.

The site starts from the starter, a small-business Astro project with services, a blog whose posts name the services they are about, and business details. It is a skeleton to adapt: a site removes what its business does not need and adds what it does. description and locale are written into its business details.

The first build starts by itself. Read the content model once that build is ready, then fill the content in.

A new site is a draft: free to edit and to share through preview links, published once it is on the Site plan. A workspace holds up to 10 drafts (25 once it has paid for a Site or credits); Sites are not counted. Past that, creating one is refused with a 409 conflict that names the limit.

Authorizations

Authorizationbearerin headerrequired

Body

application/jsonrequired
namestringrequiredlength: 1–80 chars
slugstringlength: 3–40 chars

The address: .atelier201.page. Derived from the name when omitted.

descriptionstringlength: ≤ 400 chars

One or two sentences about the business, written into the starter's business details.

localeenum<string>one of: en, fr, de, es, it, pt

Response

application/json

Create a site

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.