Atelier201 websiteJoin the waitlist
Using the productPlans and credits
Using the product

Plans and credits

What each site plan includes, and what credits pay for.

Creating a site is free; putting it online is paid. A draft is created, edited and shared through preview links at no cost, and only a site on the Site plan goes live. Each site is paid on its own. The workspace has no plan: it only buys optional AI credits, and pays one subscription for its Sites.

Site plans

DraftSite
Price per site, per month (excluding VAT)09 EUR
Or per year (excluding VAT)090 EUR, two months free
OnlineNo: preview links onlyYes
AddressPreview links, 7 days by default, 30 at most<slug>.atelier201.page and custom domains
Custom domains03
Media storage100 MB5 GB
Built site (pages, scripts, styles)200 MB, 10,000 files1 GB, 30,000 files
Time one build may take5 minutes10 minutes
Sized for visits a monthNot online50,000
AI credits added each month01,000
Publications kept for rollback550

A workspace can hold 10 drafts, or 25 once it has paid for a Site or for credits. Sites are never limited. Publishing a draft is refused with a 403 feature_not_available whose action_url opens the site’s plan.

Traffic is never a cut-off. Past its visits, the owner is told and offered an add-on.

Add-ons for a Site

A Site that outgrows its plan takes as many units as it needs. Add-ons are coming soon.

Add-onOne unit addsPrice per month (excluding VAT)
More traffic100,000 visits a month10 EUR
More storage25 GB of media3 EUR

Reading, editing, building, previewing and publishing are part of the plan. They cost no credits on any surface: the app, the REST API, MCP and the CLI. So do free stock photos and videos.

A Site whose plan ends, at the end of the period already paid, goes offline on every address: visitors see a page saying the site is taking a break, with a link for its owner (HTTP 503, so search engines keep its pages for a while). Its draft, its history and its preview links stay, and it comes back as it was when the plan is paid again. A failed payment does not take a site offline at once: Stripe retries it for about two weeks first.

What credits pay for

Credits pay for AI, and nothing else: the AI assistant in the app, and images and videos made with AI for a site. The assistant reads the site, proposes changes that you apply, and asks you questions. An AI agent you connect through MCP, the CLI or the API uses its own model, so it spends no Atelier201 credits, unless it makes an image or video with AI and its credential has the media:generate permission.

An image or video made with AI costs a fixed price per model, shown before it is made: in the assistant on the card you approve, through the API and MCP as an estimate that costs nothing. A failed generation gives its credits back. Some examples:

WhatCredits
A quick draft image (p-image)8
A photo in standard quality (flux, nano-banana)88 to 126
A high-quality image with text in it (gpt-image)320
A 5-second ambient video (p-video, 768p)438
A 5-second realistic video (wan, 720p)1,250
An 8-second cinematic video with sound (seedance, 720p)4,624

When the balance runs out, the assistant stops and tells you. Everything else keeps working.

Where credits come from

You buy credits in any amount from 10 EUR, VAT excluded. Up to 25 EUR, 1,000 credits cost 1 EUR; past that, each credit costs less the more you buy, down to 0.65 EUR per 1,000. For example, 50 EUR buys 52,900 credits and 200 EUR buys 246,600. Every AI model is available to everyone, and the assistant charges what the AI uses. Members are unlimited.

SourceWhenExpires
Welcome credits5,000, once per person90 days
Paid sites1,000 per Site, each time a site invoice is paid35 days
Bought creditsWhen you buy them12 months
Referral rewardThe new workspace on signup, the referrer on the first purchase90 days

Credits are spent oldest expiry first, so nothing expires unused while a longer-lived grant sits untouched.

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.