Websites
A website is the top-level container for design surfaces, objects, settings, files, and access. Everything on a website is pure-schema-driven: the same models and editors power every site, with no hidden per-site logic, so behavior stays consistent and recreation (from templates or exports) stays faithful. New websites start in preview mode until a subscription is active.
Templates
A new website can start from a catalog template or blank. Templates are pure schema seeds: they copy object types, pages, roles, and related starting structure into your site. They do not hold bespoke or hidden logic, behavior comes only from the shared, schema-driven platform features you configure afterward, so recreation stays consistent.
Create a website
You can create a website from the admin panel, the REST API, or MCP. All three use the same platform account.
Admin panel
Sign in to the admin panel, open your websites list, and create a site with a name, locales, and a template (or blank).
API
POST an authorized request to the websites collection.
POST /api/v1/en/websitesUse the following request body shape:
{
"name": "My site",
"templateId": "blank",
"primaryLocale": "en-US",
"enabledLocales": ["en-US"]
}Authorization uses a Bearer token from the login endpoint. Details are in the API interface guide.
AI Agents (MCP)
Call get_templates first (no templateId lists them), then save_website with a template id or blank. See the MCP interface guide for auth.
get_templates
save_websiteWebsite features
Each website exposes the same feature areas. The short notes below link to the dedicated docs sections.
Surfaces
Page, header, footer, email, and component editors: the block catalog and shared decoration/visibility rules. Cover and contain decoration backgrounds use the image pipeline (object-fit and focal point). Repeat stays a CSS background. The first decoration loads eagerly; inactive slider slides stay lazy. Image links omit rel on internal hrefs; rel is noopener noreferrer only for an external link that opens in a new tab, unless link.rel is set. Slot slider storage is layout.slideSizeByBreakpoint, layout.align (start or center), and layout.controls (arrows, counter, dots).
Objects
Object types, entries, permissions, components, user roles, lifecycles, and picker-built calculated fields for structured app data.
Website settings
Identity, favicon and install-as-app, member web push, locales, domains, email delivery, external linking, and privacy-aware web integrations (GTM, analytics, verification tags).
Access
Platform roles and platform users who can administer the website.
Files
Uploaded files and directories used by pages, objects, and email.
Theme & layout
Theme tokens and layout settings that keep the site visually consistent.
Insights
Statistics and reports for traffic and operational visibility.