Read public content
The simplest pattern. Adata-translate attribute and a tiny script:
Submit a public booking
A booking form with a real Neural Draft submit and graceful error handling.A typed mini-client for the browser
For pages that need more than a fetch or two, this 30-line wrapper gives you typed responses without a build step.A server-side authed call (Node CLI / cron / one-off)
When you need to use your API key — never from the browser — this is the shortest possible authed call:Or — use the SDK from a one-off Node script
If you have npm available, the official SDK is the fastest path:Hand this to your AI
If your AI tool supports MCP (Claude Code, Cursor, Continue), install@neuraldraft/mcp and ask:
“This is a single-file static site. Add Neural Draft so the customer can edit hero / about / footer copy from the admin. Mark every visible text node withFor tools without MCP support (Lovable, v0, Bolt), paste the prompt block from /frameworks/lovable into their system prompt.data-translate="<section>.<field>", every image withdata-image-key, and add a build-time fetch to/v1/public/content/bulk?keys=...&lang=en&project_id={PROJECT_ID}that populates each node before paint.”
Notes
- Never put your
ndsk_live_*key in HTML. Only the public endpoints under/v1/public/*are safe to call from the browser; everything else MUST go through your server. - Use
/v1/public/content/bulk(no auth, project resolved byproject_id) for client-side reads. The authenticated/v1/content/bulkis for build-time and server-side fetches. - Rate limits apply per-project to public endpoints too — see rate-limits.