Hanzo
OpenapiProjects

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

Addresshttps://api.hanzo.ai/v1/projects/sites
MethodPOST
Operationpost_projects_sites
AuthAuthorization: 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).

FieldInTypeRequiredDescription
briefbodystringBrief is what the site should be, in plain language.
modelbodystringModel names which model writes the site.
namebodystringName is the site's display name.
slugbodystringSlug is the handle and public host label to publish under.

Response

StatusBodyMeaning
200projectsSiteDeployok

200 body — 6 fields.

FieldInTypeAlwaysDescription
deploymentIdbodystringDeploymentID is the deployment this publish recorded, for the history.
filesbodystring[]Files are the site-relative paths that were uploaded, sorted.
namebodystringName is the project's display name.
slugbodystringSlug is the project the site was published into, created on the fly when the slug was free.
statusbodystringStatus is the deployment status, "live" on success.
urlbodystringURL 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.


Projects API · All Hanzo APIs · Interactive reference

How is this guide?

On this page