Developers

Site Clinic for developers. Public API + MCP.

Add Site Clinic capabilities to your application through the API, use MCP when agent workflows are the right surface, or start with the foundation guide when the desired outcome is a finished website. Public capabilities appear here only after their contracts and safety expectations are ready for developer use.

// Get started in 30 seconds
npm install @siteclinic/api

const client = new SiteClinic({
  apiKey: 'sc_live_...'
});

const audit = await client.ada.audit('https://example.com');
Choose your surface

Two public developer paths inside one product system.

The API and MCP are public developer layers in the same product system, but they solve different integration problems. The API is the direct product surface. MCP is the agent surface built on top of stable capabilities. New capabilities do not ship into both automatically.

Public API layer

Perfect Website API

Direct integration for developers building product features, agency tooling, dashboards, onboarding flows, internal jobs, and customer-facing automation on top of Site Clinic analysis.

Best when

Choose this when your application owns the user experience and you want full control over request timing, retries, storage, UI, and downstream workflows.

Advantages
  • Call Site Clinic directly through REST, JavaScript, or Python without adding an agent layer.
  • Use one account for API keys, live and test environments, usage monitoring, billing, and quota enforcement.
  • Fit audits and health data into your existing product architecture, queues, webhooks, and reporting models.
Deliverables
  • Public endpoint families for ADA, health, AI, migration, usage, and API-key operations.
  • Official SDKs, API explorer, quickstart docs, OpenAPI reference, and structured errors with request IDs.
  • Webhooks, Stripe-backed billing, quota tracking, and self-serve key management in the developer dashboard.
Public tool layer

Site Clinic MCP

A hosted API-backed Model Context Protocol server for teams who want a reviewed agent surface when specific Site Clinic capabilities are explicitly promoted as named tools.

Best when

Choose this when developers are working through AI assistants or coding agents and want the same public API system of record exposed through a curated tool catalog as promotions land.

Advantages
  • Gives agents a curated tool layer instead of relying on brittle prompt instructions or improvised request formats.
  • Keeps the public API as the system of record while making agent workflows faster to adopt across engineering teams.
  • Lets you mix human-written product code with agent-driven analysis workflows under the same auth and quota model.
Deliverables
  • Documented MCP scaffold with Site Clinic API-key auth and the same billing surface as the API product.
  • A thin stdio wrapper over the public API, with named tool access gated by explicit capability promotion.
  • A practical bridge for internal copilots, support agents, QA workflows, and code-assistant integrations.
What is public today

Current public capability families.

Contract-ready coverage for the capability subset that has already graduated into the public developer layers.

ADA Compliance

Public ADA audit workflows and related report-generation surfaces.

Performance

Health and performance checks that are already stable enough for developer use.

AI & SEO

Current public AI and SEO analysis endpoints for promoted visibility workflows.

Migration

Migration and implementation helpers that already have bounded public contracts.

Where to manage your account

The dashboard, signup, and API explorer live at app.siteclinic.io.

Public docs, API reference, and MCP guides live here on siteclinic.io. Anything that needs to know who you are — account creation, API key management, live dashboards, the API explorer — lives on app.siteclinic.io.