Monitor questions

Kitecraft suggests 20 customer-discovery questions from your saved business profile and bounded evidence, then TypeSafe reviews relevance, overlapping needs, and coverage of the saved business use cases. Kitecraft recommends up to ten distinct, relevant questions with reasons; it does not fill the set with weak duplicates. You save up to ten for later visibility checks. Saving a nonempty selection attempts the initial visibility check automatically when collection is configured. An explicit collection pause and existing runs are preserved.

In the dashboard

Open Questions to monitor in the project sidebar, or go to /projects/questions. The first visit shows one Suggest questions action when your business profile is saved. Each suggestion states the question, why monitoring could matter, and the evidence behind it. Tick up to ten, then Save selection. Edits create revisions; archiving removes a question from selection without destroying history.

Read saved state

Examples use https://kitecraft.ai production. For local verification or a supplied preview origin, replace that origin with your configured KITECRAFT_API_URL, such as http://127.0.0.1:3100.

curl --fail-with-body "https://kitecraft.ai/api/v1/questions/$PROJECT_ID" \
  -H "Authorization: Bearer $KITECRAFT_API_KEY"

Reads are free of provider calls and return candidates, recommendations, selection, and run state. A failed generation preserves the previous saved set.

Suggest, select, and edit

curl --fail-with-body -X POST "https://kitecraft.ai/api/v1/questions/$PROJECT_ID/generate" \
  -H "Authorization: Bearer $KITECRAFT_API_KEY"
curl --fail-with-body -X POST "https://kitecraft.ai/api/v1/questions/$PROJECT_ID/select" \
  -H "Authorization: Bearer $KITECRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"selectedIds":["..."],"expectedVersion":null}'

generate runs one Muse suggestion followed by one bounded TypeSafe review, with no automatic retry or silent fallback and needs a saved business profile plus write access. Poll status until ready or failed; only a later status shows failure. select saves atomically with the current selection version; a stale version fails instead of overwriting. edit and archive take the question ID with its current revision. add takes new question text and locale; it does not require an existing ID. Initial generation permits two attempts per account; archiving questions does not reset it. All writes need an active trial or subscription.

CLI and MCP

kitecraft question status --id PROJECT_ID
kitecraft question select --id PROJECT_ID --json '{"selectedIds":["..."],"expectedVersion":null}'

MCP tools mirror the same operations: questions_status (read-only), questions_generate, questions_select, questions_edit, questions_add, questions_archive. See CLI commands and MCP tools.