Lesson plans, misconceptions and question banks between sessions
A tutor's hour is sold at a professional rate and prepared in the gaps between. The prep is the same shape every week: what does this student believe that is wrong, and what questions will surface it.
Why the mainstream APIs fail here
Question banks are locked behind publisher sites, misconception lists live in a PDF from a course you did years ago, and writing twenty questions calibrated to one student's level is an hour of unpaid work per session.
How MagmaRouter is used for this
Describe the student, the syllabus point and the misconception you suspect; get a session plan, a question ladder from easy to exam-level, and the wrong answers each question should fish for. Cap the key at your prep budget and it becomes a line on the same invoice as everything else.
A working loop
- Start from the misconception, not the topic; the lesson writes itself from there.
- Generate the question ladder, then cut half of it; five good questions beat fifteen.
- Keep one thread per student so the model remembers last week's gaps.
Prompts are not stored. A signed receipt of the hash comes back on every call, so you can prove later what MagmaRouter logged. Details are on the privacy page. Per-model prices are on /models and the pricing model is on /pricing.