Welcome to Voshi
Voshi connects your educational tool to Learning Management Systems — Canvas, Blackboard, Moodle, and any other LTI 1.3 platform — without you writing a single line of LTI code, and without you running a server.
You describe the tool you want in the dashboard's AI Builder, or upload code you wrote yourself. Voshi hosts it, puts it in front of instructors, launches it inside their courses, keeps each student's work, and sends scores to the gradebook. Your tool is a small piece of browser code that talks to Voshi through one object, the Voshi API.
Voshi is in early stages of development. These docs and the related features can and probably will change — we'll keep you appraised of changes that impact you.
Building with an AI assistant? The entire documentation is available as a single markdown file at https://myeducator-llc.github.io/voshi-docs/llms-full.txt — point your assistant at that URL and it has everything. A page index lives at /llms.txt.
How it works
- You register your tool in the Voshi dashboard — a name and a description.
- You build it. Tell the AI Builder what the learner should be doing and it writes the tool; or write the code yourself and upload the folder. Either way, the result runs immediately in the dashboard's Sandbox, a practice course where you can open your tool as a student or as an instructor.
- You add locations. A location is one thing in your tool an instructor can put in a course — a quiz, a chapter, a lab. A tool with a single activity has a single location.
- You publish. Publishing makes a numbered version of your tool that courses can adopt.
- An instructor adds your tool to a course. They pick one of your locations, and Voshi creates the link (and the gradebook column, for graded work).
- A student opens it. Voshi loads your tool inside the course page and hands it the Voshi API: who launched, which location, and where to save their work.
- Your tool reports a score (optional) with one call. Voshi puts it in the gradebook.
What Voshi gives your tool
Everything arrives on one object, api, that Voshi passes to your tool when it starts:
- Who launched: a stable user ID, whether they are a student or course staff, and their name and email when they are staff. Students are anonymous to your tool.
- Where: the course and the school.
- What: which of your locations was opened.
- Storage: four places to keep JSON data and files — per course, per location, per student, and per student-at-a-location. No database to set up.
- Grades:
api.submitGrade(), available whenever the launched location has a gradebook column.
Start building
Register a tool, build it in the AI Builder, run it in the Sandbox, and publish.
Locations, extids, and placements — the vocabulary everything else uses.
What your code is, what Voshi does for it, and the rules it lives by.
The one object your tool talks to: launch details, storage, files, and grades.
Running your own server instead
Most tools are hosted by Voshi. If your tool needs its own backend — a database of its own, server-side grading, an existing product you are connecting — Voshi can hand launches to your server over HTTPS instead. That is a different integration, with endpoints to build and a signed token to verify. It is covered in Advanced: your own server, and the choice is made once, when you register the tool.