What's public
Vidext's programmatic surface as it is today — two MCP servers, browser tools, and a machine-readable discovery layer.
Vidext turns a company's own material (documents, videos, links) into training: courses made of modules, short interactive video lessons that the company's employees take. Each customer is an organization, and its knowledge is the source material it has uploaded and Vidext has processed into searchable text. People build courses in the app, in a chat with Vidext's agents; this page covers what you can reach from code.
Vidext's programmatic interface is built for agents. It is small on purpose: one authenticated MCP server that reads an organization's knowledge and modules, one public MCP server that reads these docs, a few browser tools, and a discovery layer that describes all of it before anyone signs in.
The surface
| Surface | Access | What it is |
|---|---|---|
| Vidext Operator MCP server | Authenticated (OAuth 2.1) | Five read tools at https://app.vidext.com/api/mcp/operator: search and read the organization's knowledge, list modules, and read legacy outline status. This is the API. See The MCP server. |
| Vidext Documentation MCP server | Public, no auth | vidext-docs at https://app.vidext.com/api/mcp/docs: list, search, and read these documentation pages. See Docs MCP server. |
| Browser tools (WebMCP) | In the browser | Tools the Vidext app registers for an in-browser agent: discovery reads on the sign-in page, and navigation helpers on signed-in pages. See Browser tools. |
| Discovery layer | Public, no auth | llms.txt, /.well-known/mcp, server cards, OpenAPI, and OAuth metadata. See Discovery endpoints. |
| Agent registration | Public, email-verified | A headless path for an agent to get a token on behalf of an existing user, described at /auth.md. See Authentication. |
| REST CRUD API | Does not exist | There is no general-purpose REST API. Unknown /api/* paths answer a JSON 404. |
/openapi.json is the contract for the public HTTP surfaces (discovery, OAuth, agent registration, and the MCP transport). It describes how to connect, not a resource API.
What the API does not do
Every Operator tool is a read. Nothing over MCP creates, builds, edits, or publishes content. Courses and modules are planned and built in the chat, where admins and members work with Vidext's agents, and a person publishes a course from the app.
Every call runs as the user who authorized the connection, inside one organization, with that user's access. Only organization admins and members can connect; learners cannot.
What you can build
- Assistant integrations. Let people search their organization's sources and find modules from Claude, Cursor, Codex, or another MCP client (connect a client).
- Grounded agents. Retrieve ranked excerpts from the organization's processed sources and read them in bounded slices (tool reference).
- Self-serve help. Point any client at the Docs MCP server so it can answer "how do I…" questions from these pages, with no sign-in.
Last updated on