Skip to main content

Documentation index: https://my.we.inc/llms.txt

WeInc API

Start AI website builds from a link, manage your clients and their projects over REST, embed the builder in your own product to generate and publish sites, and manage projects from AI clients over MCP.

Build with URL

Start a build from a shareable URL. Whoever opens the link sees your prompt and starts the build with one click. People who are signed out sign up first and come straight back to it.

https://my.we.inc/build?prompt=A%20landing%20page%20for%20a%20dentist

Embed a Build with WeInc button on your site with the button generator. Optional params: model, template.

REST API with an API key

A versioned REST API at https://my.we.inc/api/v1 for your organization's clients, their projects, templates, plans, orders, analytics and webhooks. Authenticate with an organization API key (read, write or both): Authorization: Bearer wk_….

An API key with write permission can also build: run AI turns, deploy, connect domains, load store products and cap each client's credits, with no browser. See the headless build walkthrough.

POST /api/v1/projects creates an empty project (or a copy of one of your templates) for a client who has activated their account by accepting their invitation (send it with POST /api/v1/clients/{id}/activate). Send client_email and name, plus an optional description and template_id. GET /api/v1/projects/{id}/preview returns the live site address and a builder link.

curl -X POST https://my.we.inc/api/v1/projects \
  -H "Authorization: Bearer wk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"client_email":"[email protected]","name":"Dentist site"}'

Endpoint reference — parameters, responses, errors, pagination and rate limits for the API-key endpoints. Machine-readable spec: https://my.we.inc/api/v1/docs (OpenAPI 3).

Embed / OEM: generate, publish, domains

Put WeInc building inside your product so your signed-in users never see a WeInc login. Identity is a server-to-server handoff: your backend calls POST /api/embed/session with the client ID and secret from your agency's Embed SDK settings and your user's ID, and receives an embed session token (embt_…) valid for 24 hours, plus a builder URL and a project.

  • Embedded builder — load the builder URL in an iframe: AI chat (when enabled for your embed) and the live preview, in your colours.
  • Headless — call these with the embed token and render the results yourself:
    • POST /api/v1/projects/{id}/chat — send a build or edit instruction; the result streams back.
    • POST /api/v1/projects/{id}/publish — publish. Send the built site files as builtFiles, or send nothing and the site is built on our servers (same as POST /api/v1/projects/{id}/deploy).
    • GET / POST /api/v1/projects/{id}/domains — list domains, or add a custom domain or subdomain.

Chat, deploy and domains also accept a write API key for any project that belongs to one of your clients. With an embed token, AI generation uses your organization owner's credit balance; with an API key it is billed to your organization, as on your own brand domain.

MCP server

Connect AI clients like Claude and Cursor to manage WeInc projects in plain language. The MCP endpoint lives at https://my.we.inc/api/mcp and accepts OAuth or your wk_ key. Its tools list, create and update projects, fetch preview links, list and create clients, and read templates, plans and analytics.

It does not generate sites, publish or manage domains; use the REST API with an API key or an embed session for those.