Repository navigation
Recognize NagaAI as a known custom endpoint #18127
zentixua
started this conversation in
Feature Requests & Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
NagaAI (https://naga.ac) is an API gateway whose primary API is the OpenAI Responses API. LibreChat users already add it as a custom endpoint, and it shows the generic "Custom" mark because the provider is not recognized.
Proposal, following #15664 and #17253: a
ProviderId.nagaaientry,KnownEndpoints.nagaaiwith the display name "NagaAI", host detection forapi.naga.ac, and a monochrome mark inmarks.tsdrawn withcurrentColor. No runtime routing changes: requests keep going through the existing custom endpoint path. Spec cases for the name and host inproviders.spec.tson both sides.The configuration users run today, with the Responses API turned on through a model spec:
The header limits the fetched list to models that serve the Responses API. If this is welcome, I will open an issue to take it and send one PR after it is assigned.
I work on NagaAI.
All reactions