docs: add Neon AI Gateway endpoint guide - #705
Open
mezotv wants to merge 1 commit into
Open
Conversation
|
@mezotv is attempting to deploy a commit to the LibreChat's projects Team on Vercel. A member of the Team first needs to authorize it. |
mezotv
marked this pull request as ready for review
July 26, 2026 18:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Neon AI Gateway guide under the LibreChat YAML AI endpoints docs, plus the one sidebar entry in
ai_endpoints/meta.json. Two files, insertion-only, no existing page or line is changed.Neon AI Gateway is an OpenAI-compatible inference gateway, so the guide uses nothing but the
endpoints.custommechanism LibreChat already documents for OpenAI-compatible providers. It needs no application change, and it is modelled directly on the existingnearai.mdxpage (#668).The one thing that makes it different from the other custom-endpoint pages is that the gateway host is per Neon branch rather than per account, so the guide tells readers to add one custom endpoint per branch, each with its own
name. It also covers the optionalbaseURL: "${NEON_GATEWAY_URL}"form, which works becauseendpoints.customruns bothapiKeyandbaseURLthroughextractEnvVariable.fetch: trueis used in the main example because the gateway implementsGET /v1/models.Two small choices worth flagging:
https://<your-neon-branch-host>rather than a real-looking hostname, matching the existingazure.mdxplaceholder style. It sits inside code fences everywhere it appears so MDX does not read it as JSX.icon:frontmatter key. I did not add a provider icon component.resolveIconreturnsundefinedfor a missing key, so the sidebar entry degrades to text rather than breaking. Happy to add an icon in this PR if you would prefer the page to match its siblings.Testing
Both CI jobs were reproduced locally on this branch:
pnpm install --frozen-lockfile(lockfile unchanged)pnpm exec fumadocs-mdxpnpm lint:prettier— passpnpm typecheck— passpnpm lint— passpnpm test— 184 tests in 21 files passpnpm build— pass; the page is prerendered at/en/docs/configuration/librechat_yaml/ai_endpoints/neonand itsllms.mdxroutepnpm exec playwright test— 23 passedlycheewith the exact arguments from.github/workflows/links.yml— 3 links, 3 OKCaveats
Translations
English only. Per the README,
.mdxis the source of truth and the locale files are generated, so I have left the translations to thepnpm translateworkflow rather than hand-writing them.