Discovery and well-known endpoints
The public, machine-readable documents that let an agent understand Vidext, find its MCP servers, and learn the auth contract before signing in.
Vidext publishes a discovery layer on the app domain, https://app.vidext.com. Every document here is public and needs no token. They are generated by the same code that serves the MCP servers, and the tool lists in them come from the servers' own tool definitions.
These describe the Vidext product. This documentation site publishes its own llms.txt, llms-full.txt, and a markdown version of every page (append .md to a page URL) describing the docs themselves.
The fastest route for an agent that meets Vidext cold: read /llms.txt, follow /.well-known/mcp to the endpoint, and let the 401 challenge drive OAuth. Well-behaved MCP clients do the last two steps on their own.
Start-here files
| Path | What it is |
|---|---|
/llms.txt | The product summary for language models: what Vidext does, the MCP tools, and links. The canonical entry point. |
/llms-full.txt | Everything in llms.txt, plus per-tool detail, auth endpoints, and operating guidance. |
/agents.md | When and how an agent should use Vidext. |
/agent.txt | A short pointer file: discovery, docs, endpoint, auth. |
/index.md | The homepage as markdown. |
/api/llms.txt | API and MCP discovery only. |
/developers/llms.txt | Integration guidance only. |
Requests for the homepage or the sign-in page that ask for text/markdown, or that come from a known AI crawler or agent user agent, get /index.md instead of HTML. Those responses vary on Accept and User-Agent; browsers are unaffected.
Product and trust pages
| Path | What it is |
|---|---|
/about | The company behind Vidext: legal entity, what the product does, where to go next. |
/contact | Contact channels and addresses. |
/privacy | How data is handled, with links to the policy pages. |
/developers | The developer guide: connecting, environments, rate limits, errors, versioning and deprecation. |
/pricing.md | Plans, as markdown. |
/compare, /alternatives, /best-ai-learning-path-generator-for-employee-training | Comparison pages, as markdown. |
Each page in this table also answers at a .md suffix (/about.md, /developers.md). Every served markdown document opens with --- frontmatter carrying its title, description, canonical URL, and last-updated date. /auth.md is the exception: it sends its canonical URL in a Link header instead.
MCP discovery
| Path | What it is |
|---|---|
/.well-known/mcp | MCP discovery JSON for the Operator server: endpoint, transport, protocol versions, auth pointers, tool names. Its documentationServer entry describes the public Docs MCP server at /api/mcp/docs. |
/.well-known/mcp/server-card.json | The Operator server card, with each tool's input schema and annotations. |
/server.json | Server metadata in the MCP registry format. |
/card.json | A compact JSON product card. |
/.well-known/agent-skills/index.json | Agent Skills index, serving the Vidext Operator skill at /.well-known/agent-skills/vidext-operator/SKILL.md. |
/.well-known/ard.json | Agentic Resource Discovery catalog: the two MCP servers, the Operator skill, the OpenAPI contract, and the docs, as urn:air: entries anchored to the publishing domain. |
/.well-known/ai-catalog.json | The same catalog under its earlier name. |
Every .well-known JSON document also answers at a .md suffix (/.well-known/mcp.md) with the JSON wrapped in markdown.
Vidext does not advertise A2A: /.well-known/agent-card.json answers 410.
API contract
| Path | What it is |
|---|---|
/openapi.json | OpenAPI 3.1 contract for the public HTTP surfaces: discovery routes, OAuth, agent registration, and the MCP transport. A transport contract, not a REST resource API. |
/.well-known/openapi.yaml | The same contract as YAML. |
/.well-known/api-catalog | RFC 9727 linkset of the public API surfaces, including both MCP servers. |
Auth metadata
| Path | What it is |
|---|---|
/.well-known/oauth-protected-resource/api/mcp/operator | Protected-resource metadata for the Operator endpoint: the document the 401 challenge points at. /.well-known/oauth-protected-resource serves the root version. |
/.well-known/oauth-authorization-server | Authorization-server metadata with every OAuth endpoint. The same single document is served at /.well-known/oauth-authorization-server/api/auth (where RFC 8414 looks when you start from the issuer, https://app.vidext.com/api/auth) and /api/auth/.well-known/oauth-authorization-server. |
/.well-known/openid-configuration | OpenID discovery, also at /.well-known/openid-configuration/api/auth and /api/auth/.well-known/openid-configuration. |
/auth.md | Headless agent registration (see Authentication). |
JWKS disambiguation
/.well-known/jwks.json is the LTI key set. The OAuth issuer's key set for MCP tokens is /api/auth/jwks.
Crawling, links, and not-found
/robots.txtallows search and AI input and opts out of AI training (Content-Signal: search=yes, ai-input=yes, ai-train=no), and points at/sitemap.xml.- The homepage, the sign-in page, and
/developerssend aLinkheader pointing at the sitemap,llms.txt, the developer guide, OpenAPI,server.json, the API catalog, and the skills index. The sign-in page also sends aWWW-Authenticatehint naming the protected-resource metadata, for scanners that start there. - An unknown
/.well-known/*path answers a real404asapplication/problem+json, pointing at the sitemap andllms.txt, never a sign-in redirect. For a visitor who is not signed in, a path that no organization owns answers404(as markdown, unless the client asks for HTML) instead of redirecting to sign-in. Unknown/api/*paths answer a JSON404.
Last updated on