Add video response support documentation to API playground

api-playground/overview.mdx

@@ -14,7 +14,9 @@
 
 The playground is automatically generated from your OpenAPI specification or AsyncAPI schema so any updates to your API are automatically reflected in the playground. You can also manually create API reference pages after defining a base URL and authentication method in your `docs.json`.
 
+The playground supports rich media responses including images, audio, and video content. When your API returns media content types, the playground automatically renders them inline for immediate preview.
+
 We recommend generating your API playground from an OpenAPI specification. See [OpenAPI Setup](/api-playground/openapi-setup) for more information on creating your OpenAPI document.
 
 ## Getting started
 
@@ -78,7 +80,7 @@
     <Expandable title="playground" defaultOpen="True">
     <ResponseField name="display" type="&quot;interactive&quot; | &quot;simple&quot; | &quot;none&quot;">
         The display mode of the API playground.
         - `"interactive"`: Display the interactive playground.
         - `"simple"`: Display a copyable endpoint with no playground.
         - `"none"`: Display nothing.
 
@@ -124,7 +126,7 @@
 }
 ```
 
 This example configures the API playground to be interactive with example code snippets for cURL, Python, and JavaScript. Only required parameters are shown in the code snippets, and the playground prefills the request body with example values.
 
 ### Custom endpoint pages
 
@@ -136,12 +138,39 @@
 - Add additional content like examples
 - Control playground behavior per page
 
 The `x-mint` extension is recommended so that all of your API documentation is automatically generated from your OpenAPI specification and maintained in one file.
 
 Individual `MDX` pages are recommended for small APIs or when you want to experiment with changes on a per-page basis.
 
 For more information, see [x-mint extension](/api-playground/openapi-setup#x-mint-extension) and [MDX Setup](/api-playground/mdx/configuration).
 
+## Media responses
+
+The API playground automatically detects and renders media content types in responses:
+
+- **Images** (`image/*`) - Display inline with full resolution
+- **Audio** (`audio/*`) - Playable audio player with controls
+- **Video** (`video/*`) - Embedded video player with controls
+
+When your API returns a response with a media content type, the playground renders it directly in the response panel. This allows users to immediately preview generated images, audio files, or video content without downloading.
+
+### Example
+
+If your API endpoint returns a video, ensure your OpenAPI specification includes the appropriate content type:
+
+```yaml
+responses:
+  "200":
+    description: Generated video
+    content:
+      video/mp4:
+        schema:
+          type: string
+          format: binary
+```
+
+The playground will automatically render the video with playback controls when the endpoint is called.
+
 ## Further reading
 
 - [AsyncAPI Setup](/api-playground/asyncapi/setup) for more information on creating your AsyncAPI schema to generate WebSocket reference pages.