CMS

The CMS pillar is what turns a static AI-generated site into a real, editable property. Every text node and image you mark up with our conventions becomes a field in the project’s admin — no schemas, no migrations, no glue code.

What this gives you

Translation keys — dot-namespaced keys (hero.headline, pricing.tiers.0.title) with per-language values. One bulk endpoint feeds your build process.
Image keys — data-image-key="hero.background" on an <img>. The customer can swap the image in the admin; your build resolves the URL.
Brand context — voice, colors, fonts, audience exposed as a single resource. Read once at build time, or hot-fetch per request.
Register-component — turn generated HTML into an admin-editable section in one call, with data-translate keys auto-discovered.

Quick example

Read a single key, then upsert one. The SDK exposes both as one-liners.

import { NeuralDraftClient } from "@neuraldraft/sdk";

const nd = new NeuralDraftClient({ apiKey: process.env.NEURALDRAFT_API_KEY! });

// Read one key (response includes `all_locales` with every translation)
const hero = await nd.content.get("hero.headline", { lang: "en" });
console.log(hero.value);

// Upsert (creates if missing). Free.
await nd.content.set("hero.headline", "Welcome to Acme", "en");

# Bulk-read for build time (up to 200 keys per call)
curl "https://api.neuraldraft.io/v1/content/bulk?keys=hero.headline,hero.subhead,cta.label&lang=en" \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY"

# Upsert one key
curl -X PUT https://api.neuraldraft.io/v1/content/hero.headline \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lang":"en","value":"Welcome to Acme"}'

Bulk read response shape:

{
  "hero.headline": "Welcome",
  "hero.subhead": "We build software that scales.",
  "cta.label": "Get started"
}

Seed many keys at once with bulkCreate (idempotent — existing keys are skipped, not failed):

await nd.content.bulkCreate(
  {
    "hero.headline": "Welcome",
    "hero.subhead": "We build software that scales.",
    "cta.label": "Get started",
  },
  "en",
);
// => { created: ["hero.headline", "hero.subhead", "cta.label"], skipped_existing: [] }

CMS writes are free. Content, page, component, gallery and image writes through the API or MCP use no credits (rate limits apply). Credits are only used when Neural Draft’s AI does the work, such as translating a key (10 per language). See Credits and pricing.

Common workflows

1. Build-time fetch for SSG

Static-site generators (Next.js, Astro, Nuxt, Hugo) call /v1/content/bulk once per locale at build time. Cache the response — re-fetch only when the content.changed webhook fires.

2. The client edits the live site

Texts and pictures marked with data-translate, <nd-text> or data-image-key are editable in the admin’s visual editor (Website → Edit site) and by chat in Claude or ChatGPT, without a rebuild. A static build that reads /v1/content at build time should rebuild on the content.changed webhook; a site hosted on Neural Draft or using nd.js updates by itself. See Editable markup and Client editing.

3. AI registers a generated section

When the AI in your editor generates a hero, it calls register_component(html, intent) via MCP. The component appears in your admin instantly:

POST /v1/components/register
{
  "html": "<section data-component='hero'><h1 data-translate='hero.headline'>Welcome</h1></section>",
  "intent": "marketing hero"
}

{
  "component_id": "cmp_2NgcaXxFqLPo",
  "editor_url": "https://app.neuraldraft.io/components/cmp_2NgcaXxFqLPo",
  "keys_created": ["hero.headline"]
}

The admin auto-discovers hero.headline as an editable text field. No schema work.

4. Translate a key into N languages

SDK

const job = await nd.content.translate("hero.headline", ["fr", "de", "es"]);
const finished = await nd.jobs.poll(job.id);
// finished.status === "completed"

cURL

curl -X POST https://api.neuraldraft.io/v1/content/hero.headline/translate \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target_langs":["fr","de","es"]}'

Returns a Job reference. Poll /v1/jobs/{id} (or nd.jobs.poll(id)) until terminal, or subscribe to the content.changed webhook to get notified once each language lands. Charges 10 credits per target language (translate_language).

5. Brand context for AI prompts

Read brand once, pass it into your AI calls. The MCP server does this for you; if you’re calling the API directly:

SDK

const brand = await nd.brand.get();
// Patch a field — `null` clears it.
await nd.brand.update({ voice: "friendly_professional" });

cURL

curl https://api.neuraldraft.io/v1/brand \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY"

{
  "voice": "friendly_professional",
  "audience": "indie founders building with AI tools",
  "content_tone": "warm",
  "colors": {
    "primary": { "hex": "#7C3AED", "name": "Purple" },
    "secondary": { "hex": "#0F172A", "name": "Ink" },
    "accent": { "hex": "#A78BFA", "name": "Lavender" }
  },
  "fonts": { "heading": "Inter", "body": "Inter" },
  "default_language": "en",
  "target_languages": ["en", "fr", "de"],
  "requires_branding_badge": false
}

Conventions

The two attributes the AI uses everywhere:

<h1 data-translate="hero.headline">Welcome</h1>
<p data-translate="hero.subhead">We build software that scales.</p>

<img data-image-key="hero.background" src="..." alt="...">

Keys are case-sensitive, dot-namespaced, and lowercase by convention. Index keys for arrays follow section.field.0.subfield.

Per-page SEO meta

Search engines and social cards need per-route metadata — <title>, <meta name=description>, and the og:* tags. Neural Draft stores this on the page itself so each route can have its own values without polluting the translation-key namespace. There are two surfaces depending on what kind of content you’re rendering:

CMS-managed pages — `GET /v1/pages/{slug}`

For everything that isn’t a blog post (homepage, about, services, legal, landing pages…), fetch the Page resource at build time and use the meta fields directly. Every field is nullable; an empty meta_title means the page title is used as the document title.

curl https://api.neuraldraft.io/v1/pages/about \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY"

import { NeuralDraftClient } from "@neuraldraft/sdk";

const nd = new NeuralDraftClient({ apiKey: process.env.NEURALDRAFT_API_KEY! });

const page = await nd.pages.get("about");
// =>
// {
//   id: 42,
//   slug: "about",
//   title: "About us",
//   type: "landing",
//   is_homepage: false,
//   is_active: true,
//   meta_title: "About — Acme",
//   meta_description: "We build software that scales.",
//   og_image: "https://cdn.example.com/og/about.jpg",
//   canonical_url: null,
//   ...
// }

// Create a page with SEO meta in one call (free)
await nd.pages.create({
  slug: "about",
  title: "About us",
  type: "landing",
  meta_title: "About — Acme",
  meta_description: "Built by makers who hate boilerplate.",
  og_image: "https://cdn.example.com/og/about.jpg",
});

// List pages (filter by type / is_active)
const { data: pages } = await nd.pages.list({ page_size: 50, type: "landing" });

Use nd.pages.update(id, { meta_title: null }) (or pass null via cURL) to clear a single meta field. Untouched fields are preserved — the API merges the patch into the existing record.

Blog posts — `GET /v1/blog-posts/{slug}`

Posts have their own per-translation meta. The locale-aware response picks the matching translation for meta_title / meta_description. Use featured_image for og:image (it’s the canonical image associated with the post).

curl "https://api.neuraldraft.io/v1/blog-posts/5-minute-breathwork-for-anxious-mornings?lang=en" \
  -H "Authorization: Bearer $NEURALDRAFT_API_KEY"

const post = await nd.blogPosts.get("5-minute-breathwork-for-anxious-mornings", { lang: "en" });
// post.meta_title, post.meta_description, post.featured_image

To patch SEO meta on a post (e.g. tighten the description after publish):

await nd.blogPosts.update(post.id, {
  meta_title: "5-minute breathwork — Acme blog",
  meta_description: "A 5-minute morning routine to take the edge off anxiety.",
});

Where to put what in your `<head>`

<title>{page.meta_title ?? page.title}</title>
<meta name="description" content={page.meta_description ?? ""} />
<meta property="og:title" content={page.og_title ?? page.meta_title ?? page.title} />
<meta property="og:description" content={page.og_description ?? page.meta_description ?? ""} />
<meta property="og:image" content={page.og_image ?? defaultOgImage} />
{page.canonical_url && <link rel="canonical" href={page.canonical_url} />}
{page.exclude_from_search && <meta name="robots" content="noindex" />}

For a blog post the same template applies, swapping page.og_image with post.featured_image.

Images

Image keys bind a stable key to a picture URL:

// Upload a File / Blob / Buffer (free, sync)
await nd.images.upload("hero.background", file, { filename: "hero.jpg" });

// Point a key at an existing URL (free, sync)
await nd.images.replace("hero.background", { url: "https://cdn.example.com/x.jpg" });

// Resolve / list / delete
const img = await nd.images.get("hero.background");
const { data } = await nd.images.list({ prefix: "hero.", page_size: 50 });
await nd.images.delete("hero.background");

upload() and replaceFile() accept a Web File/Blob or a Node Buffer/Uint8Array (pass opts.filename for raw buffers). AI image generation (POST /v1/images with a prompt, or regenerate) is retired and answers 410 media_generation_moved: we don’t offer AI image or video creation. We craft finished static ads and reels for your brand.

Reference

Endpoint	Tag
`GET /v1/content`	Content
`GET /v1/content/bulk`	Content
`GET /v1/content/{key}`	Content
`PUT /v1/content/{key}`	Content
`DELETE /v1/content/{key}`	Content
`POST /v1/content/{key}/translate`	Content
`POST /v1/components/register`	Components
`GET /v1/components`	Components
`GET /v1/pages`	Pages
`GET /v1/pages/{idOrSlug}`	Pages
`POST /v1/pages`	Pages
`PATCH /v1/pages/{id}`	Pages
`DELETE /v1/pages/{id}`	Pages
`GET /v1/brand`	Brand
`PATCH /v1/brand`	Brand
`GET /v1/images`	Images
`GET /v1/images/{key}`	Images
`POST /v1/images` (multipart upload)	Images
`PUT /v1/images/{key}` (multipart or URL swap)	Images
`DELETE /v1/images/{key}`	Images
`POST /v1/newsletters/subscribe` (public)	Forms
`GET /v1/newsletters`	Forms
`DELETE /v1/newsletters/{id}`	Forms
`POST /v1/contact-forms` (public)	Forms
`GET /v1/contact-forms`	Forms
`DELETE /v1/contact-forms/{id}`	Forms

Most AI-built sites need two simple capture surfaces: an email-collector for newsletters and a free-form contact form. Neural Draft ships both as first-class endpoints — no schemas to design, no spam-handling glue, and free (no credits charged, since these are storage + delivery, not AI).

Public submit

The submit endpoints are public. Authenticate the project with a server-side API key in X-NeuralDraft-Project-Key (or pass ?project_id= for unauthenticated client-side embeds where you don’t want to ship a key):

# Newsletter — idempotent. Re-submitting an existing email returns 200 with
# status="already_subscribed" instead of an error.
curl -X POST https://api.neuraldraft.io/v1/newsletters/subscribe \
  -H "X-NeuralDraft-Project-Key: $NEURALDRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"jane@example.com","app_lead":false}'

# Contact form — `data` is free-form JSON for whatever your form collects;
# IP and user-agent are merged in server-side for spam triage.
curl -X POST https://api.neuraldraft.io/v1/contact-forms \
  -H "X-NeuralDraft-Project-Key: $NEURALDRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jane@example.com",
    "subject": "Demo request",
    "message": "We are evaluating Neural Draft for our next launch.",
    "data": {"company":"Acme","headcount":12}
  }'

Reading submissions

Form submissions are not in the outgoing-webhook event whitelist today — poll the admin list endpoints (GET /v1/newsletters, GET /v1/contact-forms) or use the MCP tools list_newsletter_subscribers / list_contact_form_submissions to inspect what came in. We may add newsletter.subscribed / contact_form.submitted topics to the webhook whitelist in a future release; subscribe to the changelog if you’d like to be notified.

Admin list & delete

Listing and deleting submissions requires an API key with forms:read / forms:write scope (or *). Both list endpoints support ?page / ?page_size (max 200) and ?search=; the newsletter list also accepts ?app_lead=true to filter out trial leads from your real subscriber list.

Get started

Build with AI

Sites

Agencies

Features

SDK and API

Snippets

What this gives you

Quick example

Common workflows

1. Build-time fetch for SSG

2. The client edits the live site

3. AI registers a generated section

4. Translate a key into N languages

5. Brand context for AI prompts

Conventions

Per-page SEO meta

CMS-managed pages — `GET /v1/pages/{slug}`

Blog posts — `GET /v1/blog-posts/{slug}`

Where to put what in your `<head>`

Images

Reference

Public submit

Reading submissions

Admin list & delete

​What this gives you

​Quick example

​Common workflows

​1. Build-time fetch for SSG

​2. The client edits the live site

​3. AI registers a generated section

​4. Translate a key into N languages

​5. Brand context for AI prompts

​Conventions

​Per-page SEO meta

​CMS-managed pages — GET /v1/pages/{slug}

​Blog posts — GET /v1/blog-posts/{slug}

​Where to put what in your <head>

​Images

​Reference

​Forms — newsletter & contact

​Public submit

​Reading submissions

​Admin list & delete

What this gives you

Quick example

Common workflows

1. Build-time fetch for SSG

2. The client edits the live site

3. AI registers a generated section

4. Translate a key into N languages

5. Brand context for AI prompts

Conventions

Per-page SEO meta

CMS-managed pages — `GET /v1/pages/{slug}`

Blog posts — `GET /v1/blog-posts/{slug}`

Where to put what in your `<head>`

Images

Reference

Forms — newsletter & contact

Public submit

Reading submissions

Admin list & delete