Skip to main content
Kynva is a deterministic design engine. The same input always produces byte-identical pixels. That property — determinism — is what makes the API safe to use in production pipelines, A/B systems, and CI.

​
The pipeline

​
What this means for you

A Spec is content-addressable. If you keep the Spec, you can re-render the exact pixels months later. There are no model temperature surprises.
Every compile step writes a decisions log: why this font, why this color, which fallback fired. Audit trails come for free.
Drafts are versioned. Branch a Draft, tweak the brief, recompile. The expensive part (render) is skipped until you preview.
Style-lock rules in your BrandKit are enforced at compile time. If a brief asks for a color that violates the lock, the compiler rejects it with STYLE_LOCK_VIOLATION — before any pixels render.

​
The API surface

One canonical endpoint, two modes:

​
Sync preview

The response carries the rendered image URLs. Best when someone is waiting.

​
Async render

Consume the job via webhooks, the status poll, or the SSE stream. Best for pipelines and batches — see the async guide.

​
Signed image URLs — the shortcut

URLs that render on first fetch and cache forever. Built for OG images and no-code embeds — no Authorization header needed at fetch time.

​
What you’ll meet across every endpoint

Authentication

Authorization: Bearer kyn_live_... on every request.

Idempotency

Idempotency-Key: <uuid v4> on every POST mutation.

Versioning

X-API-Version: 2026-01-01 pins the response shape.

Rate limits

Tiered per endpoint category, surfaced in headers.