Generates a self-contained, mobile-responsive static site from a…
Generates a self-contained, mobile-responsive static site from a natural-language brief and deploys it live in one call.
POST /v1/projects/sites
| Address | https://api.hanzo.ai/v1/projects/sites |
| Method | POST |
| Operation | post_projects_sites |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Generates a self-contained, mobile-responsive static site from a natural-language brief and deploys it live in one call.
One inference call turns brief (capped at 8 KiB) into a file manifest, which
then runs through the SAME validation, guards and viewport guarantee as a
hand-supplied manifest: index.html required at the root, absolute and
traversal paths rejected, per-file and total size capped, and a mobile
viewport meta tag injected into every HTML document that lacks one. The
generated site is fully inline — no CDNs, no remote fonts or images — so it is
CSP-safe. slug and name are optional: the model's own title is preferred,
and a slug is derived or minted when none is given.
It writes into the SAME org-scoped store as /v1/projects — it ensures a
project (framework static) for the resolved slug and records a deployment —
so this is a second door onto one publish pipeline, not a second copy of
project state. Ordering is the billing contract: the hosting gate runs BEFORE
any inference or upload, so a denied gate generates and uploads NOTHING, and
the debit lands once, only after the site is actually live. The tokens are
billed to the same ledger the hosting fee was reserved against.
Answers 503 when object storage or inference is unconfigured, and 400 when the model's manifest cannot be parsed or fails the guards.
Scope: a validated principal is required (403 without one) and the site is published into THAT principal's org.
Request
4 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
brief | body | string | — | Brief is what the site should be, in plain language. |
model | body | string | — | Model names which model writes the site. |
name | body | string | — | Name is the site's display name. |
slug | body | string | — | Slug is the handle and public host label to publish under. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | projectsSiteDeploy | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
deploymentId | body | string | — | DeploymentID is the deployment this publish recorded, for the history. |
files | body | string[] | — | Files are the site-relative paths that were uploaded, sorted. |
name | body | string | — | Name is the project's display name. |
slug | body | string | — | Slug is the project the site was published into, created on the fly when the slug was free. |
status | body | string | — | Status is the deployment status, "live" on success. |
url | body | string | — | URL is the canonical live URL, https://<slug>.<apex> — empty when the subdomain belongs to another tenant and this site has none. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, ProjectsApi } from 'hanzoai';
const api = new ProjectsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProjectsSites({ brief: "<brief>", model: "<model>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProjectsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProjectsApi(client).post_projects_sites(brief="<brief>", model="<model>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ProjectsAPI.PostProjectsSites(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, projects_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = projects_api::post_projects_sites(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProjectsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ProjectsApi(client).postProjectsSites();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/projects/sites \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"brief": "<brief>",
"model": "<model>"
}'The door reaches projects through the projects tool, which names its 48 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_projects"
}
}
}'How is this guide?