Enough to set up a share and to call one.
Documentation is intentionally minimal for the pilot: how a faculty member sets up their first share, how a student calls the API, and an API reference that tracks the OpenAPI spec. More will follow as the platform moves through its summer phases.
Faculty quick start
Sign in, create a course, build a share from a scenario, order a few transformations, issue per-student API keys, and reveal the manifest when the assignment is over.
Student quick start
You have an API key. Here is the base URL, the bearer header, the watermark and records pattern, the read-only SQL endpoint, and the MCP server for agent workflows. Responses are JSON only.
API reference
A summary of every faculty and student endpoint, with auth, request, and response shape, kept in step with the hand-authored OpenAPI 3.1 spec.
Faculty admin
The faculty quick start is performed inside the admin app. You can open it directly to sign in.
How the platform works
For the conceptual model, clean data first then ordered transformations, and the manifest as the answer key, see How it works.