If you already have a portal, do not rebuild tribes, CBT, chat, and an AI tutor. Call TribePeer from your server. Learners stay inside the product you designed.
This is the path for teams who will write code. Schools that want a finished portal should look at Campus. Sites that only need a chat bubble should look at the widget.
Create tribes, publish modules, and push quizzes or assignments without standing up a second content database.
Join codes, enrollments, members, and results — scoped to your organisation, not the public social feed.
Communities, threads, and messages so a cohort has a room that is not a WhatsApp export.
Optional. Turn on TribeMate when you want Ask, quiz generation, or curriculum help inside your own UI.
Your server holds a client id and secret. It asks TribePeer for a short-lived token, then calls the classroom. People who log into your product get their own user token after a verified email. Browsers never hold the secret.
If nobody on your team will open a terminal, start with Campus or the website widget. The API is a product for builders — it is not a hidden discount on a finished school portal.