# Vidext developers

Vidext exposes a public discovery surface for AI clients that need to understand the product before authenticating.

`https://io-test.vidext.com` is an internal Vidext environment, not offered to customers or integrators. Use production: https://app.vidext.com.

## Start here

- Read [llms.txt](https://io-test.vidext.com/llms.txt) for the full product summary.
- Read [developers](https://io-test.vidext.com/developers) for integration guidance.
- Read [auth.md](https://io-test.vidext.com/auth.md) for agentic registration.
- Discover the MCP server at [/.well-known/mcp](https://io-test.vidext.com/.well-known/mcp).
- Inspect the machine-readable contract at [/openapi.json](https://io-test.vidext.com/openapi.json).

## Integration flow

1. Fetch discovery metadata from [/.well-known/mcp](https://io-test.vidext.com/.well-known/mcp).
2. Follow OAuth metadata from [/.well-known/oauth-authorization-server](https://io-test.vidext.com/.well-known/oauth-authorization-server).
3. Authenticate with OAuth 2.1 authorization-code + PKCE.
4. Connect to the shared MCP endpoint at `https://io-test.vidext.com/api/mcp`.
5. If the agent is running inside an authenticated Vidext browser page, use browser-local `document.modelContext` tools instead of remote OAuth MCP for page navigation and module lookup.

## Public assets for developers

- [/developers](https://io-test.vidext.com/developers)
- [/openapi.json](https://io-test.vidext.com/openapi.json)
- [/server.json](https://io-test.vidext.com/server.json)
- [/.well-known/api-catalog](https://io-test.vidext.com/.well-known/api-catalog)
- [/api/llms.txt](https://io-test.vidext.com/api/llms.txt)