API · Website fulfillment

AI-built websites

A WEBSITE line item is fulfilled by the AI builder: we generate a complete site (pages + blog) from the line item's metadata, host it, and hand your customer a chat-based editor to refine and publish it. One site per line item — quantity must be 1; order multiple sites as separate line items.

Send more than the minimum — it shows

Only businessName and domain are required, but generation quality scales with input. You already hold two high-value fields from the domain purchase: pass location (city/region — unlocks neighborhood references and local color) and collect an optional twoLiner on your order form (“describe your business in your own words” — it becomes the site's core promise). A creative-director pass expands whatever you send into a full brief before generation, filling gaps with confident niche-informed choices.

Fulfillment output

Once the order reaches FULFILLED (typically under a minute), each line item's fulfillment.output carries:

{
  "siteUrl": "https://portland-cupcakes.sites.jsys.com",
  "adminUrl": "https://edit.… /login?site=portland-cupcakes",
  "adminEmail": "user@example.com",
  "thumbnailUrl": "https://assets.… /thumbnails/<siteId>/<rev>.png"
}

siteUrl — the live site, served on its own subdomain. Link it from your order-confirmation page.
adminUrl — your customer's editor sign-in. Their login email is adminEmail.
No password in the payload. We email the customer a single-use set-password link (7-day expiry) directly. Credentials never transit the order API or webhooks.
thumbnailUrl — may initially be a branded placeholder; the real screenshot is captured asynchronously and merged in. Poll GET /v1/orders/:id if you need the final image.

The end-customer flow

You place the order with the customer's email + business metadata.
We generate and publish the site, then email the customer their set-password link.
They sign in to the editor and make changes by describing them — “make the headline bolder”, “add a coupon banner” — with a live preview, undo, and an explicit Publish step.

Sites speak MCP

Every published site exposes a read-only Model Context Protocol endpoint at {siteUrl}/mcp, plus /llms.txt and JSON-LD structured data. AI agents (Claude, or anything MCP-capable) can read the business info, pages, and blog content losslessly — your customers' sites are first-class citizens of the agentic web, not just HTML.

# Try it against any published site:
claude mcp add --transport http my-site https://<slug>.sites.jsys.com/mcp

Custom domains

v1 hosts every site at {slug}.sites.jsys.com. White-label hosting under your own domain (e.g. mywebsite.yourregistrar.com via CNAME) is on the roadmap — the intended design is a per-site custom-domain mapping with automatic certificates. Talk to us if you need it prioritized.

↳ Orders API · Webhooks