While working on a personal project that interfaces with the /api/conversation/process REST API endpoint, I encountered some challenges while following the Conversation API documentation to understand the request/response schema. When I received the first response, I noticed it was using the default local agent instead of my configured external LLM provider.
After searching for a way to specify the agent, I couldn’t find this information in the official documentation. Eventually, I located the needed attribute through this thread - thanks to @linusk for sharing this information.
I noticed that the complete schema, including all supported attributes, required fields, optional parameters, and data types, is already defined in the codebase. Given that these schemas are already well-defined in code, implementing an automated OpenAPI specification generator for the entire API would ensure documentation stays synchronized with the codebase and provide developers with comprehensive, standardized API references.
You’re on to something… 