Courses & training
Teachable
Course content, coupons, emails and comments on any plan.
15 endpoints
Ruzuku's API key only connects its Zapier integration, and there is no Ruzuku MCP server (checked 16 Nov 2026). Cotlet runs a hosted Ruzuku MCP server with 29 tools that ChatGPT and Claude use in your own course site: cohorts, price points, enrollments, assignments, meetings and messages. Anything students see or pay waits for your OK.
29 tools Read and write
Ruzuku documents an API key, API secret and site URL only for connecting Zapier, which passes new students, completions and payments to other apps. There is no general API for building courses or managing students, and no Ruzuku MCP server or official ChatGPT or Claude connector was found.
| What you need | Zapier key | By hand | Cotlet |
|---|---|---|---|
| New students to your email list | A Zap on each enrollment | Export and import | export_student_data on request |
| Copy a cohort, set prices and seats | Not covered | Several Manage Course screens | Your agent, after your OK |
| Assignments, meetings and messages | Not covered | One student at a time | 29 tools, student-facing writes ask first |
| Ask ChatGPT or Claude | No MCP server | Copy and paste | Hosted MCP server |
Checked 16 Nov 2026. Sources: Ruzuku integrations overview · Set up Zapier integration · Ruzuku pricing · Help: Create a course · Help: Copy a course · Help: Archive a course · Help: Browse and add Instant Courses · Help: Create a module · Help: Create a lesson · Help: Copy a lesson · Help: Delete a module or lesson · Help: Add content to lessons · Help: Add downloadable files to lessons · Help: Create and configure quizzes · Help: Create course-wide discussion forums · Help: Customize your course style · Help: Build your sales page · Help: Create and manage price points · Help: Offer free trials for your course · Help: Offer discounts and free trials with coupons · Help: Create and sell course bundles · Help: Add upsells to your course checkout · Help: Create and sell digital products · Help: Open or close a course for enrollment · Help: Set enrollment limits for your course · Help: Send free invitations · Help: Enroll students who paid outside Ruzuku · Help: Bulk Enrollment in Courses/Bundles · Help: Process a refund for a student · Help: Remove a student from a course · Help: Add a facilitator to your course · Help: Schedule course-wide messages · Help: Schedule meetings for live sessions · Help: Review student assignments · Help: Use chat for 1:1 communication · Help: View your course dashboard · Help: View student details, payments, and progress · Help: Export student data to CSV · Help: Download site-wide data · Help: Download meeting recordings · Help: Back up your course
Once, in a browser we host for you.
One address in its settings.
It drafts; you approve what students see or pay.
Your agent works in your own signed-in Cloud Browser. Messages, refunds, enrollments and anything students see wait for your OK. Who can see your session
Sign in to Ruzuku in a Cloud Browser. Open app.ruzuku.com in your Cotlet Cloud Browser and log in with your own instructor or admin account.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Ruzuku is served from the shared https://cotlet.dev/mcp/v1, along with every other app you enable, so one connector is enough. Enabled Ruzuku after connecting? Refresh the connector and its 29 tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: ruzuku_read Built from the Ruzuku Help Center, one tool per Manage Course screen. Outline work no student sees yet runs at once; everything students see or pay asks first.
Revenue, enrollments and waiting work per course, each student's progress and payments, CSV exports, recordings and backups.
The Course Dashboard is the course's home base: revenue earned, students enrolled, who signed up recently, and comments and assignments waiting for your attention. It changes nothing.
MCP callruzuku_read → view_course_dashboard
REST endpointGET https://cotlet.dev/api/v1/ruzuku/course-dashboards/view
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
{
"course": "course"
} {
"course": "Spring Watercolor Cohort",
"revenue": 5346,
"students": 18,
"recent_signups": [
"Student P",
"Student Q"
],
"waiting": {
"comments": 4,
"assignments": 3
}
} Reads Manage Course > Students: who is enrolled, how far each student has got, and whether their payments went through. Use it when a student says they cannot find the course, or before a live session to see who finished the last module.
MCP callruzuku_read → list_students
REST endpointGET https://cotlet.dev/api/v1/ruzuku/students
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| student string | string | One student. Leave empty for the whole list. |
{
"course": "course"
} {
"course": "Spring Watercolor Cohort",
"students": [
{
"name": "Student P",
"enrolled": "2026-11-02",
"progress": "9 of 12 lessons",
"payment": "Paid, $297"
},
{
"name": "Student Q",
"enrolled": "2026-11-10",
"progress": "2 of 12 lessons",
"payment": "Payment plan, 1 of 3"
}
]
} The course export covers who enrolled, when, what they paid and their progress. On Pro, Manage Site > Courses > Export Signups / Payments covers every course and instructor: the payments file has email, signup date, amount, currency, price point and course; the signups file has name, email, profile fields, signup date, status and course.
MCP callruzuku_read → export_student_data
REST endpointGET https://cotlet.dev/api/v1/ruzuku/student-datas/export
| Name | Type | Description |
|---|---|---|
| scope string required | string | `course` or `site` (Pro, admins). |
| course string | string | For `course`. |
| file string | string | For `site`: `payments` or `signups`. |
| from string | string | For `site`: ISO start date. Empty exports everything. |
| to string | string | For `site`: ISO end date. |
{
"scope": "scope"
} {
"scope": "site",
"file": "payments",
"from": "2026-10-01",
"to": "2026-10-31",
"rows": 41,
"csv": "ruzuku-payments-2026-10.csv"
} Ruzuku records its built-in Video Conference and Presentation meetings by default, and Zoom recordings upload through the Zoom integration. External meeting types have no recording in Ruzuku.
MCP callruzuku_read → download_meeting_recording
REST endpointGET https://cotlet.dev/api/v1/ruzuku/meeting-recordings/download
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| meeting string required | string | Meeting title. |
{
"course": "course",
"meeting": "meeting"
} {
"course": "Spring Watercolor Cohort",
"meeting": "Week 3 live demo",
"recording": "week-3-live-demo.mp4",
"students_can_download": true
} Returns the backup file Ruzuku produces for the course. Nothing in the course changes.
MCP callruzuku_read → export_course_backup
REST endpointGET https://cotlet.dev/api/v1/ruzuku/course-backups/export
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
{
"course": "course"
} {
"course": "Spring Watercolor Cohort",
"backup": "spring-watercolor-cohort-backup.zip"
} New, copied and Instant Courses, modules and lessons, lesson content and downloads, quizzes, forums and style.
A copy keeps all modules, lessons and content but never the students, so a new cohort starts clean. Instant Courses are 30+ ready-made templates with modules and lessons. A new course has sign-ups closed until you open them, so this runs without asking.
MCP callruzuku_write → create_course
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/courses
| Name | Type | Description |
|---|---|---|
| action string required | string | `create`, `copy` or `add_instant`. |
| title string required | string | Title of the new course. |
| from_course string | string | For `copy`: the course to copy. For `add_instant`: the Instant Course to add. |
| copy_sales_page boolean | boolean | For `copy`: bring the sales page along. |
{
"action": "action",
"title": "title"
} {
"action": "copy",
"title": "Autumn Watercolor Cohort",
"from_course": "Spring Watercolor Cohort",
"modules": 6,
"lessons": 12,
"students": 0
} Archiving moves the course out of your active list; content, settings and student data stay, and you can unarchive at any time. Deleting a course is permanent and is not offered here. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → archive_course
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/course/archive
| Name | Type | Description |
|---|---|---|
| action string required | string | `archive` or `unarchive`. |
| course string required | string | Course title as your Courses page shows it. |
{
"action": "action",
"course": "course"
} {
"course": "Spring Watercolor Cohort",
"archived": true
} Modules are the chapters or weeks of a course; lessons sit inside them and hold the content. A copied lesson leaves the original where it is. New outline items carry no content yet, so this runs without asking.
MCP callruzuku_write → build_course_outline
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/course-outline/build
| Name | Type | Description |
|---|---|---|
| action string required | string | `add_module`, `add_lesson` or `copy_lesson`. |
| course string required | string | Course title as your Courses page shows it. |
| module string required | string | Module title; for `add_module`, the new one. |
| lesson string | string | Lesson title, for `add_lesson` and `copy_lesson`. |
| to_course string | string | For `copy_lesson`: the course to copy into, if not this one. |
{
"action": "action",
"course": "course",
"module": "module"
} {
"course": "Spring Watercolor Cohort",
"module": "Week 4: Layering",
"lessons": [
"Glazing basics",
"Practice sheet"
]
} Ruzuku cannot recover deleted modules or lessons. If you only want it out of sight, Ruzuku suggests hiding the module instead. The agent names exactly what goes before it deletes. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → delete_module_or_lesson
REST endpointDELETE https://cotlet.dev/api/v1/ruzuku/module-or-lessons
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| module string required | string | Module title. |
| lesson string | string | Lesson title. Leave empty to delete the whole module. |
{
"course": "course",
"module": "module"
} {
"course": "Spring Watercolor Cohort",
"deleted": "lesson",
"module": "Week 4: Layering",
"lesson": "Practice sheet"
} Ruzuku's lesson editor combines several content types on one page, and downloads appear as links near the bottom of the lesson. Enrolled students see the change, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → add_lesson_content
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/lesson-contents
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| lesson string required | string | Lesson title. |
| blocks array | array | Content in order: text, video, audio, embed or discussion prompt. |
| downloads array | array | Files from your media library to list as download links; up to 2 GB each on Core, 4 GB on Pro. |
{
"course": "course",
"lesson": "lesson"
} {
"course": "Spring Watercolor Cohort",
"lesson": "Glazing basics",
"blocks": 3,
"downloads": [
"Week-4-Worksheet.pdf"
],
"saved": true
} Added through the lesson's Assessments section as type Quiz. Quizzes check understanding, add accountability and can gate certificates. You review the questions in the lesson before students reach it, so this runs without asking.
MCP callruzuku_write → create_quiz
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/quiz
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| lesson string required | string | Lesson title. |
| questions array required | array | Question text (up to 4,096 characters) and answer choices (up to 2,048 each), with the correct one marked. |
| passing_score number | number | Percent needed to pass; with a required lesson it gates progress, and on Pro the certificate. |
{
"course": "course",
"lesson": "lesson",
"questions": "questions"
} {
"course": "Spring Watercolor Cohort",
"lesson": "Glazing basics",
"questions": 4,
"passing_score": 75,
"saved": true
} Course-wide forums live in their own section of the course navigation, apart from lesson discussions. Students see a new forum at once, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → create_discussion_forum
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/discussion-forums
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| category string required | string | Forum name. |
| prompt string | string | Opening text students see. |
{
"course": "course",
"category": "category"
} {
"course": "Spring Watercolor Cohort",
"category": "Share your wins",
"created": true
} Style controls what students see when they open the course. The agent reads the current style first, so another call can put it back. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → customize_course_style
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/course-style/customize
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| changes object required | object | Color scheme, font, banner image URL or logo URL. |
{
"course": "course",
"changes": "changes"
} {
"course": "Spring Watercolor Cohort",
"color_scheme": "Sage",
"font": "Serif",
"saved": true
} Sales page, price points and trials, coupons, bundles, checkout upsells, digital products, and when sign-ups are open.
Every course has a sales page with its title, description and price points with enrollment buttons. Ruzuku's advice is to lead with what students will be able to do after the course. The page is public, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → edit_sales_page
REST endpointPATCH https://cotlet.dev/api/v1/ruzuku/sales-page
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| description string | string | New description with headings, lists, links and images. Leave empty to read. |
{
"course": "course"
} {
"course": "Autumn Watercolor Cohort",
"sales_page": "https://example.ruzuku.com/courses/autumn-watercolor",
"saved": true
} Students enroll through price points, and a new one is live as soon as it is created. Payment plans, subscriptions and free trials need Stripe; PayPal takes single payments only. Ruzuku charges no transaction fee on any plan. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → manage_price_points
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/price-points/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list` or `create`. `list` only reads. |
| course string required | string | Course title as your Courses page shows it. |
| type string | string | For `create`: `free`, `single`, `payment_plan` or `subscription`. |
| amount number | number | Price, or the amount per installment. |
| installments number | number | For `payment_plan`. |
| trial_days number | number | For `payment_plan` and `subscription`: free trial before the first charge. |
{
"action": "create",
"course": "Autumn Watercolor Cohort",
"type": "payment_plan",
"amount": 109,
"installments": 3
} {
"course": "Autumn Watercolor Cohort",
"price_points": [
{
"type": "single",
"amount": 297
},
{
"type": "payment_plan",
"amount": 109,
"installments": 3
}
]
} A coupon changes what students pay at checkout, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → create_coupon
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/coupons
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| code string required | string | The coupon code. |
| discount string required | string | The discount, as Ruzuku's coupon form asks for it. |
{
"course": "course",
"code": "code",
"discount": "discount"
} {
"course": "Autumn Watercolor Cohort",
"code": "EARLYBIRD",
"created": true
} Bundles suit certification tracks and discounted packages, for example three $97 courses for less than $291. Buyers see the price, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → create_bundle
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/bundles
| Name | Type | Description |
|---|---|---|
| name string required | string | Bundle name. |
| courses array required | array | Courses in the bundle. |
| price number required | number | Bundle price. |
{
"name": "Jane Doe",
"courses": "courses",
"price": 1
} {
"bundle": "Watercolor path",
"courses": [
"Fundamentals",
"Layering",
"Landscapes"
],
"price": 247,
"created": true
} Students see the upsell when they enroll in the course. It changes checkout, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → add_checkout_upsell
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/checkout-upsells
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| offer string required | string | The course, bundle or product to offer. |
{
"course": "course",
"offer": "offer"
} {
"course": "Fundamentals",
"offer": "Layering",
"added": true
} Digital products are standalone items with no modules, lessons or progress tracking, available on Pro sites. Once on sale it is public, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → create_digital_product
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/digital-products
| Name | Type | Description |
|---|---|---|
| name string required | string | Product name. |
| files array | array | Files from your media library. |
| price number required | number | Price. |
{
"name": "Jane Doe",
"price": 1
} {
"product": "Color mixing guide (eBook)",
"price": 19,
"created": true
} Ruzuku stops new sign-ups once the seat limit is reached and notifies you as the course fills. Free invitations still get through a full course. Opening a course lets the public enroll, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → set_enrollment
REST endpointPUT https://cotlet.dev/api/v1/ruzuku/enrollment
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| signups_open boolean | boolean | The Sign-ups Open toggle. |
| seat_limit number | number | Up to 20,000. Empty leaves enrollment unlimited. |
| full_message string | string | What the sales page shows when the course is full. |
{
"course": "course"
} {
"course": "Autumn Watercolor Cohort",
"signups_open": true,
"seat_limit": 20,
"enrolled": 0
} Invitations and bulk enrollment, refunds and removals, facilitators, messages, live meetings, assignments and private chat.
Each person gets an email with a single-use enrollment link and is in the course as soon as they click it. Ruzuku skips anyone already enrolled or invited. Invitations reach people by email, so the agent lists the addresses first. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → invite_students
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/students/invite
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| emails array required | array | Up to 1,000 addresses at a time. |
{
"course": "course",
"emails": "jane@example.com"
} {
"course": "Autumn Watercolor Cohort",
"sent": 3,
"skipped": [
"student.p@example.com"
]
} Bulk Enrollment is a Pro feature for admins, made for a whole cohort, a company team or a group that paid outside Ruzuku. It enrolls everyone at once, so the agent shows the count and the course first. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → bulk_enroll_students
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/enroll-students/bulk
| Name | Type | Description |
|---|---|---|
| course_or_bundle string required | string | Course or bundle title. |
| emails array required | array | Up to 1,000 addresses. |
{
"course_or_bundle": "course or bundle",
"emails": "jane@example.com"
} {
"course_or_bundle": "Team onboarding",
"enrolled": 42,
"already_enrolled": 3
} Refunds go through Stripe at once and usually reach the card in 5 to 10 business days. PayPal refunds are made in PayPal, not in Ruzuku. A refund does not remove course access: that is remove_student. Money leaves your account, so it always waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → refund_student
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/student/refund
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| student string required | string | Student name or email, as list_students returns it. |
| amount number | number | For a partial refund. Empty refunds the whole payment. |
{
"course": "course",
"student": "student"
} {
"course": "Spring Watercolor Cohort",
"student": "Student Q",
"refunded": 109,
"processor": "Stripe",
"access": "unchanged"
} The student at once loses access to lessons, modules, meetings and discussions. Their discussion posts stay visible to other students, and removing does not refund anything. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → remove_student
REST endpointDELETE https://cotlet.dev/api/v1/ruzuku/students
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| student string required | string | Student name or email, as list_students returns it. |
{
"course": "course",
"student": "student"
} {
"course": "Spring Watercolor Cohort",
"student": "Student Q",
"access": false
} Facilitators see students and progress, moderate discussions, review assignments, message students and run meetings; they cannot change settings, pricing or sales pages. They need a Guide or Admin account first. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → add_facilitator
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/facilitators
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| person string required | string | A Guide or Admin user on your Pro site. |
{
"course": "course",
"person": "person"
} {
"course": "Spring Watercolor Cohort",
"facilitator": "Teaching assistant",
"added": true
} Messages live under Manage Course > Content. Welcome and Invitation are system emails; drip courses also have Start of Module. Every message reaches all enrolled students, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → schedule_course_message
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/course-message/schedule
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| subject string required | string | Email subject. |
| body string required | string | Text; custom fields such as {{{give-name}}} fill in per student. |
| send_at string | string | ISO date and time. Empty sends now. |
| system_message string | string | To edit `welcome`, `invitation` or `start_of_module` instead of sending a custom message. |
{
"course": "course",
"subject": "subject",
"body": "body"
} {
"course": "Spring Watercolor Cohort",
"subject": "Live demo moved to Thursday",
"recipients": 18,
"send_at": "2026-11-17T09:00:00"
} Video Conference lets everyone join with video and audio; Presentation lets only the instructor share. Both can show uploaded PDF slides. Students see the meeting in the course, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → schedule_meeting
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/meeting/schedule
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| title string required | string | Meeting title. |
| start string required | string | ISO date and time. |
| duration_minutes number required | number | Set it longer than the session; built-in recordings run for the scheduled time. |
| type string | string | `video_conference` (default), `presentation`, `zoom` or `external`. |
| record boolean | boolean | Built-in types record by default. |
{
"course": "course",
"title": "title",
"start": "start",
"duration_minutes": 1
} {
"course": "Spring Watercolor Cohort",
"title": "Week 4 live demo",
"start": "2026-11-20T18:00:00",
"duration_minutes": 75,
"type": "video_conference",
"record": true
} Each submission shows the student, the lesson, the answers, the time and its status: Pending, Approved or Rejected. Save & Send Feedback emails the student your feedback and the status, so a review waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → review_assignments
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/assignments/review
| Name | Type | Description |
|---|---|---|
| action string required | string | `list` or `review`. `list` only reads. |
| course string required | string | Course title as your Courses page shows it. |
| student string | string | For `review`. |
| feedback string | string | For `review`. |
| status string | string | For `review`: `approved` or `rejected`. |
{
"action": "action",
"course": "course"
} {
"course": "Spring Watercolor Cohort",
"pending": [
{
"student": "Student P",
"lesson": "Glazing basics",
"submitted": "2026-11-15T21:04:00"
},
{
"student": "Student R",
"lesson": "Glazing basics",
"submitted": "2026-11-16T07:30:00"
}
]
} Chat is private between you and the student; other students cannot see it, unlike discussions. It reaches the student, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callruzuku_write → send_chat_message
REST endpointPOST https://cotlet.dev/api/v1/ruzuku/chat-messages
| Name | Type | Description |
|---|---|---|
| course string required | string | Course title as your Courses page shows it. |
| student string required | string | Student name or email, as list_students returns it. |
| text string required | string | The message. |
{
"course": "course",
"student": "student",
"text": "text"
} {
"course": "Spring Watercolor Cohort",
"student": "Student Q",
"sent": true
} Your signed-in Ruzuku browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 29 Ruzuku tools. The session cookie stays in the Cloud Browser.
The courses, students and payments your Ruzuku role can open. A facilitator login sees only the teaching side of its courses.
Your Stripe, PayPal, Zoom and Zapier connections, your Ruzuku plan and billing, and course deletion. PayPal refunds stay in PayPal.
You log in again yourself, in the same Cloud Browser.
Disable Ruzuku for agents, reset the browser, or change your Ruzuku password.
Cotlet never sees or stores your password: you log in to Ruzuku yourself, and the agent only uses the session it leaves. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the Ruzuku server when Ruzuku changes its screens, so your agent keeps working without any code on your side.
Your Zapier Zaps keep running as they are. The agent works next to them, inside the course site, and changes no integration settings.
If Ruzuku logs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.
| Action | How to put it right |
|---|---|
| Course archived by mistake | Unarchive it with archive_course |
| Sign-ups opened too early | Close them with set_enrollment |
| Module or lesson deleted | Ruzuku cannot recover it: hide modules instead when unsure |
| Refund or course message sent | Already with the student: follow up yourself |
21 of the 24 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 that only build course structure, create_course, build_course_outline and create_quiz, run at once, as do the 5 read tools.
{
"name": "manage_price_points",
"arguments": {
"action": "create",
"course": "Autumn Watercolor Cohort",
"type": "payment_plan",
"amount": 109,
"installments": 3
}
} curl -X POST https://cotlet.dev/api/v1/ruzuku/price-points/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","course":"Autumn Watercolor Cohort","type":"payment_plan","amount":109,"installments":3}' {
"course": "Autumn Watercolor Cohort",
"price_points": [
{
"type": "single",
"amount": 297
},
{
"type": "payment_plan",
"amount": 109,
"installments": 3
}
]
} The example adds a payment plan of 3 × $109 next to the $297 single payment; payment plans need Stripe. A cron job or n8n flow can make the same call over REST at /api/v1/ruzuku with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a creator running two live cohorts, 3,570 credits. Your Ruzuku plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning dashboard and assignment list, two courses | 4 × 30 | 1,200 |
| Assignment feedback sent | 1 × 40 | 400 |
| 1:1 chat replies | 1 × 20 | 200 |
| Live meetings scheduled | 1 × 8 | 80 |
| Course-wide messages | 1 × 8 | 80 |
| Invitations for students who paid elsewhere | 1 × 6 | 60 |
| Next cohort: copy, two price points, seat limit | 4 × 1 | 40 |
| Month-end payments export | 1 × 1 | 10 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 207 calls | 3,570 |
The smallest pack, 5,000 credits for $29, covers this month. More cohorts or more assignments mean more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Ruzuku Zapier integration | API key, secret and site URL connect Zapier; Zaps pass new students, completions and payments to other apps. | Moves data out; it does not build courses, review assignments or message students. |
| Stripe and PayPal dashboards | Payments and refunds on the processor side. | No course access: removing a student stays in Ruzuku. |
| By hand | Manage Course, one screen and one course at a time. | Only while you are at the desk. |
Keep Zapier for sending new students to your email tool. Cotlet fits when you want ChatGPT, Claude or a script to work inside Ruzuku, from your own login, with nothing to host.
Take Group sp. z o.o. builds and runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, and its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Ask about the Ruzuku tools at contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=ruzuku, turn on Ruzuku under Integrations in the console and log in at https://app.ruzuku.com/ in your Cloud Browser. Then connect your AI agent and ask it what is waiting in your courses. The trial needs no card.
Ruzuku documents an API key, API secret and site URL only for connecting its Zapier integration, which automates enrollments, completions and payments into other apps (checked 16 Nov 2026). It publishes no general API for building courses, enrolling or messaging students, and no Ruzuku MCP server or official ChatGPT or Claude connector was found. Cotlet does not use that key: it works in your own signed-in Ruzuku account.
Most tools work on every plan. Free invitations need Core or Pro; bulk enrollment, facilitators, digital products and the site-wide export need Pro. Ruzuku lists Free for up to 5 students, Core at $99 a month and Pro at $199 a month, with no transaction fees (ruzuku.com/pricing, checked 16 Nov 2026).
No. Keep the Zaps that copy new students to your email tool or log payments to a sheet. Cotlet covers work inside Ruzuku that Zapier does not reach, such as copying a cohort or reviewing assignments.
No. In Ruzuku a refund and course access are separate, and the tools keep them separate: refund_student returns the money through Stripe, remove_student switches access off. The agent does each only after your OK.
Only in how it is called. Both carry the same 29 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Ruzuku.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy