FAQ
Short answers to the most asked questions. For technical detail, the developer docs are the reference.
Curriculum infrastructure: it turns official curricula into structured, reviewed, attributed knowledge consumed via API. Not a student platform, not a gradebook.
From official documents: publisher, authority, edition, and retrieval date on every element. We attribute no curriculum to an authority without a documented source.
No. No names, no grades, no guardian data — by design. Curriculum text submitted for review is scanned, and refused and recorded if it seems to carry personal data.
As YYYY.N.P. Published is immutable; a correction is a new version. The full number is the exact citation reference.
An API version (/v1) describes the contract shape; a knowledge version (2026.1.0) describes content. Content is pinned by the full knowledge number on every read.
With an API key made in your workspace (a test key or a live one), kept on your server. Organisations the operator runs use a service client's short-lived token, carrying one tenant and defined scopes. No keys in client code or the browser.
Yes. Signed deliveries, retried on failure, for three of the contract's nine events: a curriculum version published or deprecated, and an outcome changed. Framework releases send no event yet. The webhooks page lists what is sent.
It proposes candidates and relations only. Approval and publishing are always human, with no path from extraction to publishing without review.
Didn't find your answer?
The technical docs or email cover the rest.