Asp.net endpoints to mimik OpenAPI to allow use Web UIs

@TesAnti
Anti — Today at 4:49 PM
@HavenDV what do you think about mimiking openAI api? this will allow us to attach UI to our chain
You were mentioning LangServe
haven't looked at it yet though
HavenDV — Today at 5:03 PM
Didn't understand what you mean. Is this about implementing all the features that the OpenAI API has?
Anti — Today at 5:03 PM
actually only text completitionas ones.
this will allow us to server chains for web-UI's like this:
https://github.com/oobabooga/text-generation-webui
there is a lot of them
you can build chain that get's data trough RAG, makes google search, summarizes everythig and puts out to the user
but for user side it would be just chat and all complicated behaviour will be hidden
HavenDV — Today at 5:09 PM
yes, I have plans to do something similar to chat as an example. but not sure if the server should provide an API equivalent to OpenAI text endpoints and it's up to the client to decide. Typically this chain is implemented on the server side and only the final end points are provided. Because otherwise it opens up space for reverse engineering and using it for cracker purposes
Anti — Today at 5:21 PM
Typically this chain is implemented on the server side and only the final end points are provided
That is what i'm talking about. You implement a chain and wrap it into API which mimiking OpenAI. Then you can use any existing UI(designed for ollama, OpenAI, or anything else) to chat with your chain
HavenDV — Today at 5:58 PM
Yes, I understand you, in general this makes sense if the restrictions on the number of possible user requests per second/minute/hour/day are configured correctly
We need to create an issue about this
Anti — Today at 6:44 PM
i have seeing this as for single person use. But now when you mention this... We can make a queue of requests. This should be enough
For proper limits there should be user authorization of some sort
Also interesting thing would be not only to have API wrapper, but also whappers for bots like for Discord and Telegram

No files, tests, or entry points are named. Start by defining the supported OpenAI-compatible text-completion endpoints and how ASP.NET should expose configured chains, then review the existing server and chain APIs. Done should include an agreed scope for compatibility, request limits or queuing, authorization, and tests for the resulting API.