Key facts
| Agent stack | Chat completions, function calling and embeddings are live |
| Use cases | Tutoring, lesson planning, progress summaries, administrative drafting |
| Teacher review | Grades and student-affecting decisions stay with educators |
| Student data | Keep records and identifiers out of prompts; integrate by reference |
| Models | 30+ models including multilingual options for diverse classrooms |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped options |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Roadmap | Batch and assistants endpoints are coming soon |
TL;DR
- Tutor with retrieval over the actual curriculum, not open-web answers.
- Draft lesson plans and materials for teacher review and editing.
- Keep grading and student decisions with educators.
- Protect student records by referencing them rather than sending them.
- Measure learning impact and teacher time saved, not messages sent.
How it works, step by step
- Choose one use case such as curriculum tutoring or lesson-plan drafting.
- Index approved curriculum content and require citations to the source material.
- Expose read-only tools for content search and class resource lookup.
- Add teacher review for grading, feedback and any student-affecting output.
- Keep student records out of prompts and connect by reference where needed.
- Log tool calls and model versions, then measure learning and time-saved outcomes.
Try it yourself
Open the best model for agents selector →
Education use cases an agent can support
Educators need help with preparation and feedback, not with decisions:
- Tutoring: answer curriculum questions with citations, adjusting explanation depth.
- Lesson planning: draft objectives, activities and assessments from approved material.
- Progress summaries: turn notes and results into a digest for a teacher to review.
- Administrative drafting: letters, notices and reports from templates and structured data.
Keep the educator accountable for feedback, grading and any student-affecting action.
Architecture and student-data protection
Student data rules vary by jurisdiction and institution, so treat them as a design input:
- Curriculum retriever: embeddings over approved content so answers stay in scope.
- Read-only tools: content search, class resources and scheduling lookups.
- Composer: answers with citations and age-appropriate language.
- Teacher gate: review for grading, feedback and anything sent to students or parents.
- Records by reference: connect to student systems without copying records into prompts.
Log tool calls and model versions so behaviour can be reviewed and explained.
Safety, fairness and deployment
Test the agent for bias and inappropriate content on your own curriculum before students see it, and add a reporting route for students and staff. Keep an adult escalation path for safeguarding concerns; the agent should never be the final responder. Choose the processing region deliberately and set retention to the minimum. Where the institution requires it, deploy in a VPC, on-prem or air-gapped environment with the same compatible API, so the materials, prompts and evaluations you tested remain valid.
Pilot and evaluation
Prototype on plugsky-micro or plugsky-lite with one subject and one class, then use the 14-day full-access trial to test a stronger model on tutoring depth and lesson-plan quality. Measure teacher time saved, student engagement, answer accuracy against the curriculum and escalation quality. Self-serve plans are flat monthly with fair-use usage, which avoids term-time billing spikes. Roll out subject by subject with versioned prompts and a re-run of the evaluation whenever the curriculum changes.
Honest comparison
| Capability | Plugsky | Typical agent framework | Building in-house |
|---|---|---|---|
| Tool calling | Live function calling over content and scheduling APIs | Framework-specific adapters | You build and maintain |
| Curriculum grounding | plugsky-embed plus RAG over approved content | Add-on or external store | You integrate everything |
| Teacher gate | You enforce review for grading and student-facing output | Varies | You design controls |
| Deployment | Cloud, VPC, on-prem and air-gapped | Usually cloud-only | You operate GPUs and serving |
| Pricing | Flat monthly self-serve, fair-use usage | Varies by framework and model | GPU plus operations cost |
Frequently asked questions
Can the agent grade students?
It can assist with feedback drafts, but grades and student-affecting decisions should stay with educators who review the evidence.
Which endpoints do education agents use?
Chat completions, function calling, JSON mode and embeddings are live. Batch and assistants endpoints are coming soon.
How do we protect student records?
Keep records and identifiers out of prompts, integrate by reference, set retention deliberately and deploy in a region or environment that matches your obligations.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, suitable for a single-class pilot.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage, which helps with term-time peaks. See the live pricing page for details.
Can we host it ourselves?
Yes. On-prem and air-gapped deployment is available, and the same compatible API means your tested application runs unchanged.
How should we measure it?
Track teacher time saved, student engagement, curriculum accuracy and escalation quality rather than message volume.