Fix chat completion request body example

[OEvortex]

Summary

• update the /v1/chat/completions example body so Swagger UI shows proper parameters
• require a ChatCompletionRequest body in chat_completions

Testing

• ruff check webscout/Provider/OPENAI/api.py | head -n 5
• ruff check webscout/Provider/OPENAI/api.py | tail -n 20

[Copilot]

Pull Request Overview

This PR updates the /v1/chat/completions endpoint by revising the example request body in Swagger UI and enforcing a required ChatCompletionRequest body in the endpoint signature.

• Updated the example schema to include "messages", "max_tokens", and "temperature" parameters.
• Changed the API endpoint from accepting an optional ChatCompletionRequest via manual fallback parsing to requiring it via Body(...).

Comments suppressed due to low confidence (2)

webscout/Provider/OPENAI/api.py:612

• The removal of the manual parsing fallback means that invalid or missing request bodies will now rely on Pydantic validation. Please add tests to validate proper error responses for invalid input scenarios to ensure robust request handling.

chat_request: ChatCompletionRequest = Body(...)

webscout/Provider/OPENAI/api.py:598

• The updated schema example now excludes fields like 'model', 'choices', and 'usage'. Please ensure that the API documentation is updated accordingly to reflect the new example schema and parameter expectations.

"messages": [