# Vidext API and MCP discovery

This scoped llms.txt describes the public API discovery assets that support agent integrations for Vidext Operator.

## Primary endpoints

- OpenAPI: [/openapi.json](https://app.vidext.com/openapi.json)
- API catalog: [/.well-known/api-catalog](https://app.vidext.com/.well-known/api-catalog)
- MCP discovery: [/.well-known/mcp](https://app.vidext.com/.well-known/mcp)
- MCP server card: [/.well-known/mcp/server-card.json](https://app.vidext.com/.well-known/mcp/server-card.json)
- Registry server metadata: [/server.json](https://app.vidext.com/server.json)

## Authentication metadata

- Authorization server metadata: [/.well-known/oauth-authorization-server](https://app.vidext.com/.well-known/oauth-authorization-server)
- Protected resource metadata: [/.well-known/oauth-protected-resource](https://app.vidext.com/.well-known/oauth-protected-resource)
- Authorization endpoint: `https://app.vidext.com/api/auth/oauth2/authorize`
- Token endpoint: `https://app.vidext.com/api/auth/oauth2/token`
- Dynamic client registration: `https://app.vidext.com/api/auth/oauth2/register`

## Supported agent workflows

- Discover the operator MCP tool before auth
- Initiate OAuth 2.1 + PKCE from the MCP challenge response
- Connect to the shared MCP endpoint and select the narrowest hybrid tool
- Poll long-running workflow progress with typed `get_operation` arguments
- On authenticated app pages, use browser-local `vidext.ask_operator` when current route/module context should be passed automatically

## Related scoped context

- Product overview: [/llms.txt](https://app.vidext.com/llms.txt)
- Agent auth: [/auth.md](https://app.vidext.com/auth.md)
- Developer context: [/developers/llms.txt](https://app.vidext.com/developers/llms.txt)
- Comparison context: [/compare](https://app.vidext.com/compare)
- Category context: [/best-ai-learning-path-generator-for-employee-training](https://app.vidext.com/best-ai-learning-path-generator-for-employee-training)