Evidence boundary: LibreChat documents configurable AI endpoints in its public configuration. The evidence supports integration capability, not a statement about the maintainers' hosted production provider choices.
Documented integration pattern
- Select a documented endpoint type.
- Map the provider base URL, credentials, and model names.
- Keep endpoint configuration outside public source.
- Test capabilities and fallback behavior with the selected model route.
Relevant provider records
- OpenAI API · official channel
- Anthropic API · official channel
- OpenRouter · router channel
First-party evidence
- LibreChat endpoint configurationFirst-party endpoint configuration documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove LibreChat's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.