Your content, each learner's pace, zero manual sequencing.
Adaptcourse connects to your existing platform via REST API or LTI embed. Your content stays where it is. The engine handles question-by-question routing, prerequisite detection, and difficulty calibration without touching your infrastructure.
Dropout clusters at the same modules every cohort
When a learner hits a concept they are not ready for, they stall and drop out. Your completion metrics show where it happens. They do not show why. The answer is almost always a prerequisite gap that arrived two modules earlier, undetected.
Without adaptive pacing
- Learners hit hard modules without prerequisite foundation
- Dropout clusters at the same 2-3 modules every cohort
- No question-level data on where learners actually struggle
- Completion rates improve only by simplifying content
- Re-engagement after dropout is near zero
With Adaptcourse
- Prerequisite gaps flagged before the hard module, not during
- Learners routed through recovery paths instead of stalling
- Per-question response data feeds back to content authors
- Difficulty calibration keeps learners in the productive challenge zone
- Content improvement is guided by actual response patterns
Three integration paths, one weekend to ship
Your content stays where it is. Your platform architecture does not change. Pick the connection method that fits your stack.
REST API
POST each learner response, receive the next-node recommendation and difficulty parameter in the 200 response. Your front-end controls the question display and session UI. Full reference docs cover all endpoints, response state types, error codes, and webhook event formats.
POST /api/v1/session/next-question
Content-Type: application/json
{
"student_id": "s_8821",
"node_id": "alg_04_ratio",
"response_state": "correct",
"elapsed_ms": 14200
}
HTTP 200
{
"next_node": "alg_05_proportion",
"difficulty": 0.72,
"route_reason": "advance"
}LTI 1.3 Embed
Drop the Adaptcourse engine into any LMS that supports LTI 1.3. Students launch sessions from inside your existing platform interface. Grades and completion events post back to your gradebook via the LTI Assignment and Grade Services spec.
Tool: adaptcourse.com/lti/launch
JWKS: adaptcourse.com/lti/jwks
Deep link: per-course assignment
AGS: score + progress writeback
Compatible with:
Canvas, Moodle, Blackboard, Brightspace, Schoology
Webhook Events
Subscribe to session events and receive HTTPS POST payloads for every response, node transition, gap flag, and session completion. Use the event stream to feed your own analytics layer, trigger downstream notifications, or write completion events back to your own gradebook. Payloads signed with HMAC-SHA256, retry x3 on non-200.
session.start
response.submitted
gap.detected
node.advanced
session.complete
Delivery: HTTPS POST, retry x3
Auth: HMAC-SHA256 signature
What platform product teams need from an adaptive engine
White-label UI
The question delivery interface matches your brand: colors, typography, and logo. Learners never see Adaptcourse branding unless you choose to show it. Fully custom CSS overrides available on the District / Platform tier.
Content graph editor
Map your existing course questions into a content graph using the visual editor or the JSON import format. Define prerequisite relationships, difficulty levels, and branch conditions between nodes. No coding required for content teams.
A/B testing for question difficulty
Run controlled experiments on difficulty calibration settings within a course. Split learner cohorts by routing parameters and measure completion rates, time-to-mastery, and engagement per variant. Results feed back to the content graph editor.
Per-enrollment pricing option
Online platforms with rolling enrollment schedules can use per-enrollment billing instead of per-semester. Custom contract via the District / Platform tier. Billing only applies to active learner sessions, not to dormant enrolled accounts.
Integrate in a weekend
Tell us your platform's content graph structure and your preferred integration path. Kai will confirm the approach and provision sandbox credentials the same day. Most platforms have a working test session within 48 hours.