Current backend flow
Project generation currently starts with intake-question generation and then continues into full project generation against a draft project token.
Project generation is split across two internal sandbox routes today
Project Studio already has backend generation primitives, but the public API-key surface does not yet expose a clean versioned project create route. The docs therefore show the current internal routes and the planned public direction separately.
Current live backend
2 internal routes
Question generation and project generation both live under `/api/sandbox`.
Retriever
/api/sandbox/items/{encrypted_id}
Internal encrypted-ID retrieval route.
Planned public shape
/api/v1/projects
Preview only.
Current backend flow
Project generation currently starts with intake-question generation and then continues into full project generation against a draft project token.
Routes
What this page actually points to
/api/sandbox/generate_questions
Generate intake questions for a draft project.
Auth
Session/JWT auth in the app today
Notes
Current app route, not a public API-key route.
/api/sandbox/generate_project
Generate a full Project Studio artifact.
Auth
Session/JWT auth in the app today
Notes
Current app route, not a public API-key route.
/api/sandbox/items/{encrypted_id}
Retrieve a saved sandbox item by encrypted ID.
Auth
Session/JWT auth in the app today
Notes
Current app route, not a public API-key route.
/api/v1/projects
Planned versioned project create route described by the product design.
Auth
Planned API key support
Notes
This shape is design direction, not a shipped backend path.
Request details
Planned top-level project fields
This is the future-facing versioned shape, not a live public route yet.
Requested project or capability.
Shared context envelope.
Desired learner outcome.
Motivation or business reason.
Current learner level.
Scope or depth preference.
Related pages
Context Objects
The product design describes a shared `context` array for learner data, source documents, and Vidbyte artifacts. That envelope is already present in some request models, but the current public routes still primarily map prompt-driven fields into the existing internal orchestrators.
Quizzes
Quiz generation and progressive editing already exist in the backend under sandbox routes. The product design points toward cleaner versioned quiz endpoints, but those resource-style paths are not shipped yet for external API-key callers.
Overview
Vidbyte's API docs now separate what is live today from what is still product direction. The public API-key surface currently ships versioned create routes for quickhits and roadmaps, while quizzes, exams, and projects remain internal or preview-only.