Spirian API
In developmentThe engine, on its own.
Send one free-form mathematics question. Receive a verified, parameterised template your own system can execute. Built for platforms that already draw questions from templates and are limited by how long a person takes to author each one.
What comes back
A template, not a question.
The output is the thing a person would otherwise have sat down and authored. Your engine draws the items from it.
Parameters
Which quantities in the question vary, and the form each one takes.
Valid domain
The values those parameters may hold without the question degenerating or leaving the syllabus.
General method
The operations each step of the working requires, in order, independent of the numbers.
Worked solution
The working for a drawn variant, matching the method that was checked rather than reconstructed afterwards.
Marking rubric
Where the marks sit and what earns them, so a variant can be set as assessment and not only as practice.
Verification status
Whether the method resolved symbolically. Anything that did not is flagged and withheld rather than returned as though it had.
Where it sits
We run the other direction.
Automated Item Generation is mature and widely deployed. In every version of it, a person writes the item model and the machine writes the items. That authoring step is the constraint, and it is the step almost nobody is working on.
We call the inverse Automated Template Extraction: the derivation of a verified, executable question template directly from a single existing question, without a human authoring the template by hand. AIG runs model to items. ATE runs item to model, and then to items.
Which is why this is an API and not a platform. Existing question engines are what our output is built to run on. We are not asking anyone to replace one.
Where it is up to
There is no public endpoint yet and no documentation to read. The engine is being proven out on Australian senior secondary mathematics first, because the syllabus gives a hard, checkable boundary and a wrong answer is visible immediately. The architecture is not specific to it.
If you run a platform and this is the shape of the problem you have, we would rather talk early than pitch you late. Write to [email protected].
The rest of the line
Built on the same engine.
Spirian is the parent brand. The API is the engine exposed directly, and the products above it are the engine held a particular way.
Early access
Join the waitlist now.
Join the waitlist to get a free month when we release. First 50 only. Hurry up and secure your spot.