Preview / internal onlyReference

Exam generation is live in sandbox internals, but not yet on the versioned public API surface

Exams API

The backend can already generate exams through `/api/sandbox/create_test`, but the cleaner `/api/v1/exams` contract described by the product design remains preview-only.

Manage keys
Route-accurate reference

Current live backend

/api/sandbox/create_test

Internal app-auth route.

Validator-driven

Exam parameters

The route is already backed by exam parameter validation internally.

Planned public shape

/api/v1/exams

Still preview.

Recommended stance today

Document the exam family for product planning, but treat the public versioned contract as aspirational until the API-key route layer exists.

Routes

What this page actually points to

2 entries
POSTInternal only

/api/sandbox/create_test

Generate a full exam from content using sandbox orchestration.

Auth

Session/JWT auth in the app today

Notes

Current app route, not a public API-key route.

POSTPreview

/api/v1/exams

Planned versioned exam 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 exam fields

The stable mental model is already clear even though the public route is not live yet.

exam_settingsobjectOptional

Preset-driven exam configuration.

promptstringRequired

Assessment target or content area.

contextobject[]Optional

Shared context envelope.

Related pages

Preview / internal only

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.

Open page
Preview / internal only

Projects

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.

Open page
Preview contract

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.

Open page