Wizard — builder session HTTP API

Curated HTTP families for Blueprints Wizard automation. Authoritative route parsing lives in lenses/serve.py; the full machine-generated table is the HTTP API route catalog. Maintainer narrative prose that predates…

Updated

What it is

Curated HTTP families for Blueprints Wizard automation. Authoritative route parsing lives in lenses/serve.py; the full machine-generated table is the HTTP API route catalog. Maintainer narrative prose that predates automated inventory remains on GitHub: HTTP API and routes source.

JSON envelope

Session shape is validated by wizard-session.schema.json with a worked sample at sample-wizard-session.json (JSON examples).

Read models (safe automation)

Family Representative GET Purpose
Feature gate /api/blueprints/wizard/enabled Whether Wizard surfaces should appear
Session list /api/blueprints/wizard/sessions Hub inventory
Session body /api/blueprints/wizard/session/<id> Current envelope for builders read-only

Use Schemas and API for builders for error envelopes and safe curl habits (GET listings only in shared examples).

Write / assist paths (POST)

These mutate session state or trigger outbound work — never paste live tokens or customer data into docs.

Step Pattern (representative) Notes
Create / replace session POST /api/blueprints/wizard/session Allocates id used in deep links
Telemetry POST /api/blueprints/wizard/telemetry Step/navigation observations
Refine POST /api/blueprints/wizard/session/<id>/refine LLM assist
Interpret POST /api/blueprints/wizard/session/<id>/interpret LLM assist
Artifacts …/generate-artifacts, …/artifact-review, …/artifact-export, …/artifact-recheck Review gate before export
Launch pack …/cursor-launch-pack/<action> Editor handoff
Clarify …/clarify-suggest Suggested prompts

Exact suffix sets can grow per release — diff docs/generated/api-routes.json when upgrading.

Verify

A GET /api/blueprints/wizard/enabled from loopback matches what operators expect before you script deeper calls.

What to do next