LibreChat Custom Endpoint

Documentation maintained by 1ZheAI. Sources and corrections.

Found an error? Contact support with the page address and a description. Do not send API keys or account credentials.

LibreChat requires a deployment administrator to allow custom endpoints; ordinary users cannot rewrite remote server configuration using this site’s buttons. The console API Keys → Use Tools → LibreChat provides a configuration snippet.

Administrator Configuration

Merge into the existing librechat.yaml the endpoints.custom; do not overwrite other endpoints:

yaml

endpoints:
  custom:
    - name: '1折AI'
      apiKey: user_provided
      baseURL: 'https://1zheai.com/v1'
      models:
        default: []
        fetch: true

Apply the configuration validation required by the current version and restart the service, then have users enter their own keys in LibreChat’s API key settings. The shared configuration does not contain real keys. If model retrieval fails, the administrator can set default to a verified working model ID and check the server’s outbound network access.

Verification and Troubleshooting

Select the newly added endpoint and model, send a brief request, then check this site’s call logs. If the endpoint does not appear, first check whether the configuration mount location and restart took effect; for 401, check the key entered by the user; for 404, check that the Base URL is /v1 and not the full request path. Do not store keys on untrusted public LibreChat instances.

Official: Custom endpoint fields.

protocol and official materials verified on 2026-10-19. This site has implemented configuration generation and front-end regression testing; real inference verification across all clients, systems, and models has not been completed. Please re-verify after client upgrades. Custom integration does not imply official partnership or built-in recommendation.

More: API Keys, Model List, Call Logs, Address Notes.