Send through supported LMS paths.
Build whatever you want on top.
One platform, two jobs. Dispatch SCORM packages to verified customer LMS targets with seat caps, expiry, and revocation. Or build entirely new learning products on our hosted API — SCORM runtime, xAPI Learning Record Store, sub-tenant workspaces, all included.
# JSON in, hosted SCORM out curl -X POST https://api.allureconnect.com/v1/quick-publish \ -H "Authorization: Bearer ac_test_…" \ -d '{ "title": "Phishing Awareness · Q2", "scorm_version": "2004", "slides": [{ "title": "…", "content": "…" }] }' ← 201 CREATED { "package_id": "pkg_01hxfv9p2c4d8e6f", "launch_url": "https://app.allureconnect.com/player/public/pkg_…", "sandbox": true }
Publish a SCORM course right now.
This is the real API. Edit the JSON, hit publish, and get a hosted launch URL you can open. That URL is not an LMS-importable package; for LMS delivery, create and export a SCORM dispatch shell, then import that package into a supported SCORM-compatible LMS after verifying the target and version.
The live demo is currently unavailable.
Demo output is watermarked and rate-limited. Your own free sandbox key removes the shared limits.
One API. The 12-month build you skip.
Host and dispatch SCORM 1.2/2004 content, then capture richer learning activity through xAPI.
Send through supported LMS paths. Build whatever you want on top.
Whether a customer needs SCORM-shell delivery through a supported, target- and version-verified LMS path, or you're building a new product on our learning primitives — Connect is the runtime underneath.
Send
Dispatch SCORM packages to supported customer LMS delivery paths with seat caps, expiry, and revocation. Verify each target and version before rollout; recorded completion data returns to one dashboard.
- SCORM-shell dispatch through supported SCORM-compatible LMS paths after target and version verification; your runtime stays in control
- Allowed-domain, seat-cap, and expiry guardrails on every route
- Per-client reporting · per-dispatch revocation · audit-grade evidence
- Embedded launch URLs for your own product or marketing pages
Build
Hosted SCORM runtime, xAPI Learning Record Store, and multi-tenant session management — exposed as clean REST endpoints. Sub-tenant API lets you run a white-label LMS on top of us.
- Quick Publish API — JSON in, hosted launch URL out
- Sub-tenant API for multi-tenant SaaS · parent/child workspaces
- GPT Actions schema & agent-ready REST API · MCP server in development
- Signed webhooks · idempotency keys · per-key spend caps
Serve supported customer LMS delivery paths from one source of truth.
Stop maintaining separate course copies for each customer system. Publish once, then dispatch with seat caps, expiry, and a kill switch after verifying each target LMS and version. Review completion updates in one place.
One package. Many customers. Real licensing teeth.
Every dispatch route gets its own allowed domain, seat cap, expiry date, and revocation button. Your customer's LMS receives a tiny SCORM shell ZIP — we keep the runtime in your hands.
- →Allowed-domain enforcement · launches reject if referer doesn't match
- →Per-route seat caps and expiry dates; password challenges are planned
- →Republish a package, every active dispatch picks up the new version
- →One-click revocation — stops launches without touching the customer's LMS
Review how your content reaches learners through supported, verified LMS paths.
One package → supported destinations → completion callbacks return to one source of truth. Our dispatch fabric routes launches and reconciles supported records from verified delivery paths. The illustration below shows example routes, not compatibility proof.
The wedge: agent-native learning infrastructure.
We're building agent-native from day one: a hosted GPT Actions schema, a sub-tenant API for multi-tenant SaaS, and an agent-ready REST surface — with an MCP server in development. If you're building with AI or shipping multi-tenant SaaS, Connect is designed for you.
JSON in. Hosted SCORM out.
Send a structured course payload, get a launch URL back the same call. Idempotent. Versioned. Resumable. Watermarked in sandbox, clean in production.
- →Validated, packaged, and mounted in one response
- →Re-publish to bump versions · old launch URLs keep working
- →Output works in supported SCORM-compatible LMSs
curl -X POST https://app.allureconnect.com/api/v1/quick-publish \ -H "Authorization: Bearer ac_test_…" \ -d '{ "title": "Phishing Awareness · Q2", "scorm_version": "2004", "slides": [{ "title": "Spotting suspicious senders", "content": "Look for **misspelled domains**, urgent tone, and unexpected attachments." }] }' ← 201 Created { "package_id": "pkg_01hxfv9p2c4d8e6f", "launch_url": "https://app.allureconnect.com/player/public/pkg_…" } # Try it without a key → live demo above
Stop duct-taping SCORM infrastructure together.
Many teams assemble a runtime, LRS, dispatch shell, tenant model, and webhook pipeline separately. Connect brings those supported workflows into one hosted backend.
What you're cobbling together today
- Three versions of every course — one for each customer's LMS quirks. Update once, you update everywhere. Manually.
- Email-chased completion CSVs from your customers' L&D admins every quarter, two weeks late, in inconsistent formats.
- No way to revoke access when a customer doesn't renew. The course just keeps running in their LMS forever.
- A separate hosted runtime with its own account, usage model, and integration surface.
- An embedded standards engine that still leaves deployment, database, upgrades, and product workflows to your team.
- Custom Postgres LRS you built — works until xAPI verb cardinality blows up your queries.
- Webhook receivers, retry queues, dead-letter handling — three months of work, still flaky.
- One SCORM shell generator from a contractor — works for Cornerstone, breaks on Moodle.
- No GPT Actions. No sub-tenant API. Every AI feature is yours to build.
What you actually need
- Hosted runtime from day one. Self-serve sandbox. Production access on the Starter tier.
- Standards-based dispatch for supported LMS delivery paths, verified against each target and version before rollout.
- Built-in LRS with verb-aware indexing, anomaly detection, and audit-grade compliance evidence exports.
- Signed webhooks with automatic retry, dead-letter queue UI, and a replay button.
- GPT Actions, sub-tenant API, agent-ready REST. One documented product surface for automation. MCP server in development.
- Per active learner. No tier cliff — overage gets cheaper as you grow. Dispatch, LRS & analytics bundled in one plan.
Pay per active learner.
One ladder, free to enterprise. A generous learner allotment on every plan, overage that gets cheaper as you grow, and no tier cliff. Dispatch, LRS, and analytics bundled in.
- 25 active learners / mo
- 5 GB storage
- Full API · GPT Actions
- No credit card
- 250 active learners / mo
- then $0.15 / extra learner
- 25 courses, then $2 / prorated course-month
- Production keys, no watermark
- Email support
- 1,500 active learners / mo
- then $0.08 / extra learner
- 100 courses, then $2 / prorated course-month
- Sub-tenant API · child workspaces
- Custom domain · email support
- 7,500 active learners / mo
- then $0.05 / extra learner
- Full white-label · prepaid credits
- 500 GB · unlimited packages
Common questions
What is Allure Connect, in one sentence?
It's a hosted learning backend — SCORM runtime, xAPI Learning Record Store, dispatch engine, and API — that lets you ship content delivery and tracking infrastructure in days instead of months.
How is this different from SCORM Cloud?
SCORM Cloud supports a broader standards set today. Allure Connect focuses its current runtime on SCORM 1.2/2004 and xAPI, then adds a GPT Actions schema, an agent-ready REST API, and a sub-tenant API. The biggest difference is the billing unit: SCORM Cloud meters registrations (one learner on one course, so a learner taking three courses counts three times), while we meter active learners (one learner counted once per billing period, any number of courses). We also have no tier cliff — overage gets cheaper as you grow — and dispatch, an LRS, and analytics are bundled in every plan.
What does "agent-native" mean and why should I care?
Two things: (1) our APIs are designed to be called by AI agents — idempotent, with structured JSON in, structured JSON out, watermarked sandboxes for safe agent traffic. (2) We ship a hosted GPT Actions schema today, and an MCP server is in development, so building "an AI that creates training courses" is a config block plus an API key, not a custom integration.
Can I run my own multi-tenant LMS on top of Connect?
Yes — the sub-tenant API unlocks on Growth and up. Your parent-scoped API key can mint and manage isolated child workspaces programmatically. Usage rolls up to one billing parent. Each child gets its own custom domain, branded player, and per-child quotas. Scale and Enterprise add full white-label.
Do I have to use your hosted runtime, or can I dispatch into my customer's LMS?
Both. Hosted launch URLs are available for your own product or AI workflows — Connect serves the runtime. Dispatch supports B2B delivery through supported SCORM-compatible LMS paths after you verify each target and version. Connect generates a SCORM shell for that verified path, while launches call back to Connect.
What standards do you support?
SCORM 1.2, SCORM 2004, and xAPI 1.0.3 (Tin Can) are supported today. cmi5, LTI 1.3, and AICC package or launch support are not currently available.
Can I choose a data-hosting region?
Customer-selectable region pinning is not available today. Contact us before purchase if your organization has a specific residency requirement so we can confirm whether the current deployment is suitable.
What happens if my agent goes haywire and burns through my quota?
On current paid plans we do not block learners when usage grows. Current Starter and Growth plans can also flex above their course allowance at $2 per prorated active course-month, with combined learner and course usage capped at the next-plan price gap. Scale has no published next-plan guard, and Enterprise usage is contractual. Existing paid customers retain learner-only opt-in terms with no course charges until they upgrade to current terms. API keys remain subject to documented rate limits.
Start sending or start building today.
Free developer sandbox. Full API access from day one. Production keys on the Starter tier.