Workspaces, projects and children

A workspace owns projects, team permissions, subscription entitlements and credits. A project represents one domain and contains up to one website plus funnels. Each child (siteId in the API) has its own draftRevisionId and optional publishedRevisionId. Domain configuration, CRM, forms, calendars, assets, commerce connections and tracking defaults belong to the project. External integrations operate inside their authorized workspace and project/child permissions.

Saved revisions

Revisions are immutable website source snapshots with an increasing version. A completed build records routes and a verified artifact. Editing creates a new revision; restoring copies a previous revision into a new draft. Neither action changes the live published revision.

Tracking has project defaults and child/page overrides, separate from source revisions. Changing a shared default affects inheriting published pages; overrides retain their own configuration.

Asynchronous AI runs

Creating or editing a website returns HTTP 202 with a runId. Poll get_run using siteId and runId. Statuses include queued, running, committed, failed, and cancelled. Only a committed run has produced a saved revision. Poll every 5–10 seconds and back off on 429 or 503.

create_site and edit_site use the platform's bounded AI workflow and credit accounting through Vercel AI Gateway. create_source_site and submit_source use isolated build verification with no model calls or AI credits. External agents cannot supply provider credentials to the platform workers.

Private preview and public publishing

preview_site creates a private ten-minute URL for a saved built revision. It does not publish. Publishing selects a saved verified revision and checks plan entitlement, artifact ownership, active embedded resources, and delivery health. Preview URLs are temporary access credentials; share them only with authorized reviewers.