Fig. 1 — Agent-first publishing

Your agent builds it.
Clave puts it live.

Clave is the publishing platform built for AI agents. No login flow, no dashboard, no DNS — one token turns a built site into a live one at s-your-site.heyclave.party.

Ship your first site Read the API docs

Field record — one deploy

$ node deploy.mjs --name my-site
site site_… (my-site): 24 file(s), 3 to upload
live: https://s-my-site.heyclave.party

Detail B — the deploy, drawn to scale

How a deploy works

When your agent finishes a site, it sends Clave a list of file hashes, uploads the ones Clave doesn't have, and activates. That's the whole deploy.

Cut 01

Send the manifest

One request lists every file as a path, a sha-256 hash, and a size. Clave answers with the hashes it doesn't already have.
```
POST /v1/sites/:id/deployments
{ "manifest": { "/index.html":
  { "hash": "9f8c…", "size": 5210 } } }
→ { "id": "dep_…", "missing": ["9f8c…"] }
```
Cut 02

Upload what's missing

Files are stored by content, so only changed files travel. Redeploy an unchanged site and nothing uploads at all.
```
PUT /v1/deployments/:id/files/9f8c…
Content-Type: application/octet-stream

<the file bytes>
```
Cut 03

Activate

One more call flips the deployment live. TLS and the subdomain are already there — the response is your URL.
```
POST /v1/deployments/:id/activate
→ { "url":
  "https://s-my-site.heyclave.party",
  "status": "active" }
```

Rev A — deliberate omissions

Omitted from this drawing, by design

~~Login flow~~ Omitted
A clave_… token in the environment is the whole auth story. Agents never see a sign-in page.
~~Dashboard~~ Omitted
The API is the entire surface. Anything a console would show, a GET request already answers.
~~DNS setup~~ Omitted
The site name is the subdomain — s-your-site.heyclave.party — with TLS included, nothing to configure.

Plan view — for site owners

Ask your agent. Get a URL.

Say what you want — "build me a site for my bakery" — and your agent does the rest: builds it, checks in with you along the way, and puts it live. You never touch hosting.

The site's source and its specs stay in a repo you own. Clave only ever holds the built files — you can leave any time and lose nothing.

Start with the Clave skill

Elevation — for agent builders

An API one script can hold.

Seven endpoints, bearer auth, structured errors. The reference client is a single dependency-free Node script — the API is small enough that this is the whole integration.

It works from any agent runtime, a CI job, or plain curl. If your tool can make an HTTP request, it can publish.

Read the API reference

Sheet notes — general specifications

The proof is the mechanism

SPEC 01 Content-addressed storage: Files travel by sha-256. A redeploy of an unchanged site uploads zero bytes.
SPEC 02 Reference client: One stdlib-only Node script (Node 18+). No SDK, no dependencies, nothing to keep up to date.
SPEC 03 TLS + subdomain included: Every site serves over HTTPS at s-<name>.heyclave.party the moment it activates.
SPEC 04 Structured errors: Every error is { code, message, retryable } — an agent knows exactly when a retry is safe.
SPEC 05 Your repo is the source: Source and specs live in your git repo; the platform holds only the built files.
SPEC 06 Idempotent by design: Same manifest, same result. Deploys can be retried blindly — the safe default for automation.

Rev B — planned

On the board, not yet cut

Custom domains

Serving your site at your own example.com is coming — not yet. Today every site lives at s-<name>.heyclave.party, TLS included.

Lead-capture forms

Spam-filtered enquiry forms are coming — not yet. Today, point your call-to-action at an email, phone, or booking link; sites upgrade in place when forms land.

Nothing else to set up

Put your token in the environment and ship your first site. If your agent can make an HTTP request, it can publish.

Ship your first site Read the API docs

Your agent builds it.Clave puts it live.