Scan Results: https://hyperframes.heygen.com

My documentation is returning excessive HTML to AI agents.
Implement server-side content negotiation in my app.

When a request includes the header 'Accept: text/markdown',
return ONLY the technical content as clean Markdown.

Strip completely: navigation menus, footers, cookie banners,
sidebar links, breadcrumbs, social sharing buttons,
interactive widgets, and any HTML not containing technical content.

The response should contain only:
- Page title as H1
- Section headings as H2/H3
- Body text
- Code blocks with language tags
- Parameter tables
- No HTML tags, no CSS, no scripts

Reduce layout boilerplate (header, footers, scripts) or use Markdown Content Negotiation to strip DOM noise.

Review every code example in my documentation.
For each snippet, ensure it is fully self-contained and executable.

Every code block must include:
1. All import / require statements at the top
2. Package installation command in a comment
3. Authentication initialization if the code makes API calls
4. All variables defined before use — no undefined references
5. Inline comments explaining WHY each step is done, not just what

An AI agent copying this snippet must be able to run it
without searching for any additional information.

Details: No imports are present in the snippet. The code lacks necessary import statements or installation commands for dependencies.

Expose an OpenAPI or Swagger specification at a standard path (e.g. /openapi.json) or link to it using the "Link" HTTP response header with rel="openapi".

Embed a <script type="application/ld+json"> block classifying your docs as a TechArticle, Guide, or APIReference, containing semantically enriched metadata.

Provide a comprehensive table or section listing error codes, their causes, and solutions. This lets agents cross-reference error stacks and resolve integration errors automatically.