Thanks for your quick and concise reply.
I respect your opinion on this, however the OpenAPI spec has been useful for many years before AI (which I'd never mentioned) was in the picture. The tooling I speak of is utilizing API clients (Postman, Bruno…etc), and more importantly leveraging such specs to enforce type safety out of the box.
For example… openapi.spec → openapi-ts → generates a typesafe SDK of the LimeLM API. (assuming the spec is written correctly).
As for generated slop… I've instead created an initial spec off your HTML (via an agent), and will refine it manually to match the documents for my needs. Its only slop if you let it become so.
Best.
OpenAPI spec available for the LimeLM api?Answered
Is there an OpenAPI spec available for the LimeLM API? It would be great to have. There's a lot of tooling that can leverage this format and could help with integration.
Answer
It looks like LimeLM pre-dates OpenAPI by about a decade. A proprietary thing, bought by another company, then pawned-off to the Linux foundation because it wasn't really that useful.
Short answer, is no, our web API is well developed, well documented, with multiple examples: https://wyday.com/limelm/help/api/
The TurboActivate API is also well developed, multi-platform (Windows, Linux, macOS, BSD), and for every modern programming language: https://wyday.com/limelm/help/using-turboactivate/
Ditto the TurboFloat API: https://wyday.com/limelm/help/using-turbofloat/
I'd say just follow the examples. Making “machine readable” API specs is the last thing we want to do.
Generative-AI (slop-AI) is a technological dead-end.