Cause (Documented platform behavior): Initialization resolves key/baseURL from config or per-user stored values and throws when absent.
Fix status: documented_behavior
Limitations:
- Endpoint-rename cause inferred from lookup-by-name logic.
Other error fragments:
- Base URL not provided.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/danny-avila/LibreChat/d297530def0228607627ea4c01a6147a71f1c0c1/packages/api/src/endpoints/custom/initialize.ts (official_docs, unknown, documented_behavior): Throws Config not found, NO_USER_KEY, NO_BASE_URL, API key not provided, Base URL not provided.
Search phrasings: LibreChat API key not provided custom endpoint; LibreChat Config not found for the custom endpoint; librechat user_provided NO_USER_KEY
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Chat fails; UI prompts for key or shows error.
- Context
- Product: LibreChat Component: endpoints/custom/initialize.ts Operation: Using custom endpoints with apiKey: "user_provided" or renamed endpoints Affected versions: unknown Environment: unknown Packages: LibreChat main at pinned SHA Trigger: user_provided key not yet saved by the user (NO_USER_KEY / NO_BASE_URL), empty apiKey after substitution, or conversation references an endpoint name no longer in config.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- API key not provided.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [LibreChat] "<endpoint> API key not provided." / "Config not found for the <endpoint> custom endpoint." / NO_USER_KEY with user_provided keys
Recommended action: Have the user set the key in the endpoint key dialog, fix config apiKey, or keep endpoint names stable (conversations store endpoint name).
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 5806025c-8b10-480f-9184-33363b45b282
- Proposed action
- Recommended action: Have the user set the key in the endpoint key dialog, fix config apiKey, or keep endpoint names stable (conversations store endpoint name).
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.