Documentation

Docs for onboarding, auth, quotas, and real implementation work.

Start with Step 0 when the goal is a finished website, a client implementation, or a clear build plan. Use the API quickstart when you already know you need programmatic access and want the fastest path to a successful request.

Start here

Client Foundation

Choose the build path, confirm requirements, understand the 30-day trial boundary, separate website-build delivery from API access, and define what counts as a completed website or integration before work begins.

Open Step 0 →

API path

API Quickstart

Create a developer account, generate an API key, install an SDK, and make a first authenticated request against Site Clinic.

Open API quickstart →

Reference surfaces

Reference + explorer

The API reference lists every endpoint family. The API explorer (auth-gated at app.siteclinic.io) lets you exercise requests from the browser.

API reference API explorer

Guides

Implementation guides

Practical guides for the workflows you hit after the first successful API call.

Client Foundation

Choose the build path, confirm requirements, and understand what the API does before implementation starts.

Build Website With AI

Use the Site Clinic Web Builder standard as a copy-paste build brief for Codex, Claude Code, Cowork, or another implementation agent.

Accounts, API, MCP, DNS, and Secrets

Know which steps an AI coding agent can execute with Site Clinic API/MCP access and which steps the human owner must complete in repo, hosting, DNS, Stripe, and Google accounts.

Live + test keys, Bearer auth, rotation.

Rate Limits & Quotas

Plan limits, usage endpoints, retry patterns.

Request IDs, structured errors, failure classification.

Callback URLs, async completions, idempotent processing.

Common code paths for audits, health, AI visibility.

MCP integration

Run Site Clinic as an MCP server for agent clients.

Have a question that is not in the docs yet? Reach the developer support surface.