Bettyapp lecture moments

npx add-mcp 'https://bettyapp.org/mcp'

Bettyapp for AI tutors

Bettyapp finds the moments in university and school lectures where a topic is explained. An AI tutor (ChatGPT, Claude, Gemini, a school's own chatbot) can ask Bettyapp for the moments that explain a student's topic or question, and send the student to the lecture at that moment. The API and the MCP server are free and read-only.

What it answers

• search_moments: a topic or a question, in plain words, and if you like a Subject and a Level. It answers up to 10 moments, best first.
• get_lecture: a lecture by its id or its page's address, with all its moments.
• get_topic: a topic, with the best moment that explains it at each Level, from school to university.
• list_subjects and list_levels: the Subjects and Levels you can search in.

Each moment has its lecture, course and teacher, its Subject and Level, where it starts and ends, a title and summary and the questions it answers (where the lecture page has them), its topics, a short excerpt of what the teacher says where the licence allows it, the credit line and licence, a play address and a picture. The play address is the lecture page on Bettyapp, playing from the moment. No answer has a whole transcript.

Only lectures with a page on Bettyapp are in the answers. When an answer has no moments, Bettyapp has nothing on that topic.

The MCP server

Add this address to an MCP client (Claude, ChatGPT and others that connect to remote MCP servers by their address):

https://bettyapp.org/mcp

It speaks MCP over Streamable HTTP and needs no sign-in. Its tools are search_moments, get_lecture, get_topic and list_subjects, with descriptions written for an AI tutor, and search and fetch, the pair ChatGPT's deep research uses. For the higher limits, add your developer key as a header: Authorization: Bearer bdev_….

The REST API

Every call is a GET under https://bettyapp.org/api/v1/ and answers JSON. Any website may call it from the browser (CORS is open). The OpenAPI 3.1 description is at /api/v1/openapi.json: import it into a custom GPT's Actions, or any tool that reads OpenAPI.

Try it: click one of these links to see what the API answers.

• Search: why does ice float
• Search: photosynthesis, at High School
• Topic: chain rule, the best moment at each Level
• The Subjects and their Levels
• The Levels
• The OpenAPI 3.1 description

Every answer has an attribution line and a terms address. Follow the attribution: link the moment's play_url and show its credit.line.

Limits and keys

• Without a key: 20 calls a minute and 500 a day for each network address.
• With a free developer key: 120 calls a minute and 10,000 a day for each key.
• Short transcript excerpts also count toward the site's hourly limit on excerpts, for each key or address.

Past a limit, a call answers 429 with retry_after_seconds. Send the key in a header: Authorization: Bearer bdev_…, or X-Bettyapp-Key: bdev_…. Never put it in an address.

Get a developer key

Type your email address and what the key is for, and click Email me a key. We email you a link that works for 24 hours. Click it, then click Get my key: the key is shown once. An address may have 5 keys at a time. To stop a key, write to contact@bettyapp.org.

We keep your email address, what the key is for and when the key was last used, as the Privacy notice says.

Terms

1. The API and the MCP server are free to use.
2. Use them to send students to moments: give the student the moment's play address (play_url), which opens the lecture page on Bettyapp at that moment.
3. Include the lecture's credit line (credit.line) wherever you link a moment, and say that the moment was found with Bettyapp.
4. Do not download Bettyapp in bulk: no copying of all the lectures, topics or moments, no mirror of the site, no scraping round the limits.
5. Do not use what the API answers to train or fine-tune AI models. Many lectures are under licences that do not allow commercial use (for example CC BY-NC-SA), and they belong to their creators.
6. Use only what an answer says. When an answer has no moments, Bettyapp has nothing on that topic: do not say that it has.
7. Keep a developer key private. It goes in a request's header, never in an address or a page that others can read.
8. Bettyapp may change the limits, or stop a key that is used against these terms.

The lectures belong to their creators, under the licences their pages show (Sources and licences). Bettyapp's own Terms and copyright apply too. Questions: contact@bettyapp.org.