Skip to main content

Prerequisites

  • A KiteFrost account (sign up free)
  • Your sk_live_... API key from Settings → API Keys
  • A project id (create one in the dashboard, or via POST /v1/projects). All Game Narrative routes are project-scoped.

Step 1: Author an NPC

Define an NPC as structured, version-controlled content. You author it once; it becomes part of your project’s canon and feeds the continuity check and your exports.
Author the rest of your cast, quests, locations, factions, and items the same way (/v1/projects/{project_id}/game-narrative/story-arcs, /locations, /factions, /items).

Step 2: Run the continuity check

This is the pack’s headline feature. Point it at everything you’ve authored and it audits for cross-arc contradictions - citing the exact entity or arc each one breaks. It is advisory and read-only (it never edits or blocks your build) and free (0 Story Units; a budget-exhausted project still gets the full report).

Step 3: Export into your build

Once the report is clean, export the finished narrative into your game. Exports are build artifacts - Ink, Yarn Spinner, or universal JSON - with no per-utterance cloud call at runtime.

Advanced: runtime dialogue

Runtime dialogue is a secondary, advanced capability. Most studios author and export at dev time (Steps 1-3). Use this only if you need in-character dialogue generated on demand. It is an asynchronous call: it returns 202 Accepted with a session_id you poll for the result, and (unlike the continuity check) generation carries Story Units.

Next steps

  • Run the continuity check over your full project before every milestone
  • Generate a consolidated lore bible for your writers’ room
  • Set up Webhooks to receive generation events
  • Supply your own LLM key via BYOK to route AI drafting through your chosen provider