Discovery and well-known endpoints
The public machine-readable surface — how agents understand Vidext before authenticating.
Vidext publishes a complete discovery layer on the app domain: public, unauthenticated, machine-readable resources that let an AI client understand the product, find the MCP server, and learn the auth contract — before any token exists. All generated from one source of truth, so they always agree with the live server.
These describe the Vidext product (vidext.com). This documentation site additionally publishes its own llms.txt and per-page .md mirrors describing the docs themselves.
Start-here files for agents
| Path | What it is |
|---|---|
/llms.txt | The product summary for LLMs: capabilities, constraints, MCP tool list, links. The canonical agent entry point. |
/llms-full.txt | Everything in llms.txt plus per-tool reference, auth endpoints, and operational guidance for agents. |
/agents.md | When and how an agent should use Vidext — task-oriented instructions. |
/agent.txt | The terse pointer file: discovery, docs, endpoint, auth in a few lines. |
/index.md | Homepage as markdown, with positioning and developer resources. |
Scoped variants exist at /api/llms.txt (API/MCP discovery only) and /developers/llms.txt (integration guidance).
MCP discovery
| Path | What it is |
|---|---|
/.well-known/mcp | MCP discovery JSON: endpoint, transport, protocol versions, auth pointers, tool names. |
/.well-known/mcp/server-card.json | Pre-connection server card with tool input schemas and annotations. |
/server.json | MCP-registry-format server metadata (branding, repository, remotes). |
/card.json | Compact JSON product card. |
/.well-known/agent-skills/index.json | Agent Skills discovery index, serving the official Vidext Operator skill (SKILL.md) at /.well-known/agent-skills/vidext-operator/SKILL.md. |
Vidext does not advertise A2A. /.well-known/agent-card.json returns 410 because the Operator endpoint speaks MCP, not the A2A protocol.
API contract
| Path | What it is |
|---|---|
/openapi.json | OpenAPI 3.1 spec for the public surface: discovery routes, OAuth endpoints, and the MCP transport (including 401/429 behavior). A transport contract — not a REST CRUD API. |
/.well-known/openapi.yaml | The same spec as YAML. |
/.well-known/api-catalog | RFC 9727 linkset cataloguing the public API surfaces and their docs. |
Auth metadata
| Path | What it is |
|---|---|
/.well-known/oauth-protected-resource | Protected-resource metadata — where the 401 challenge points. |
/api/auth/.well-known/oauth-authorization-server | Authorization-server metadata listing all OAuth endpoints. |
/auth.md | The minimal headless agent-registration path (see Authentication). |
JWKS disambiguation
/.well-known/jwks.json is the LTI key set. The OAuth issuer's JWKS for MCP is /api/auth/mcp/jwks.
Using the layer well
If you are building an agent that discovers Vidext cold: fetch /llms.txt, follow /.well-known/mcp to the endpoint, let the 401 challenge drive OAuth — that exact sequence is what the layer was designed for, and what well-behaved MCP clients do automatically.
Last updated on