> I'm sorry. It's just another wrapper for a 3rd party model

The main challenge with working with LLMs is actually one of "ETL" and understanding what data to load and how to transform it into some form that leads to the desired output.

For trivial tasks, this is certainly easy. For complicated tasks, like understanding a codebase or a product catalog of tens of thousands of entries, this is non-trivial.

My team is not working in the code gen space, but even though we also "just wrap" an API, almost all of our work is in data acquisition, transformation, the retrieval strategy, and structuring of the request context.

The API call to the LLM is like hitting "bake" on an oven: all of the real work happens before that.