Probably worth thinking more about what we mean by "wrapper". A year or so ago, it often meant a prompt builder UI. There's no moat for that. But if in 2025 a "wrapper" means a proprietary data source with a pipeline to deliver it along with some proprietary orchestration along with the UI (and the LLM API being called), then it likely warrants looking at it differently.