Atelier201 websiteJoin the waitlist
REST APIAuthentication
REST API

Authentication

API keys, OAuth connections, scopes, and which credential to use.

Two kinds of credential, and the difference is not cosmetic.

API keys

A workspace service credential. Whoever holds it acts as the workspace. Only an admin can create one, and the admin chooses its scopes.

Terminal
curl https://api.atelier201.com/v1/sites \
  -H "Authorization: Bearer atelier201_live_..."

The secret is shown once, when it is created. Atelier201 stores a hash, so it cannot show it again. If it is lost, revoke it and make another.

OAuth connections

A person’s delegation to a client: an MCP client, or atelier201 auth login. It carries their identity, so it is also bounded by the workspace’s member ceiling: an admin decides how much of their own access a member may hand to a robot.

Atelier201 implements OAuth 2.1 with PKCE, dynamic client registration (RFC 7591) and the device flow. Every supported client is public, so there are no client secrets: PKCE replaces them.

Scopes

Grant the narrowest scopes the work needs.

ScopeAllows
account:readRead the workspace, its plan and its credit balance.
usage:readRead credit usage over time.
sites:readRead sites: files, content, builds, previews, history and domains.
sites:writeCreate sites, edit files and content, upload media, build and share previews. Nothing becomes public.
sites:publishPublish, roll back or take a site offline, and delete a site. This changes what visitors see.
domains:writeConnect, check and remove custom domains, and choose a site’s main address.
media:generateMake images and videos with AI, paid in the workspace’s credits at the price shown before each one.

sites:write cannot publish, and cannot spend credits: only media:generate can. An agent with it can prepare a complete site, and the owner decides when it goes live. A scope is the first check, not the only one: publishing, rolling back, taking offline, deleting a site and changing domains also need a workspace admin.

A guest site uses neither kind of credential: its short-lived write token opens that one site. See Guest sites.

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.