docs(config): document Eden AI as an EU OpenAI-compatible provider#202
Open
MVS-source wants to merge 1 commit into
Open
docs(config): document Eden AI as an EU OpenAI-compatible provider#202MVS-source wants to merge 1 commit into
MVS-source wants to merge 1 commit into
Conversation
Eden AI is a French, EU-based OpenAI-compatible gateway. OpenKB already supports it through the existing OPENAI_API_BASE override, so this documents the config in the configuration guide and .env.example: set LLM_API_KEY to an Eden AI key, OPENAI_API_BASE to https://api.edenai.run/v3 (or the EU endpoint), and a double-prefixed model (openai/<vendor>/<model>) so LiteLLM keeps Eden AI's vendor-prefixed id intact.
There was a problem hiding this comment.
Pull request overview
Documents Eden AI as an EU-based OpenAI-compatible gateway configuration for OpenKB/LiteLLM by adding concrete .env and config.yaml examples, clarifying the required openai/<vendor>/<model> (three-part) model identifier format to preserve Eden AI’s vendor-prefixed model IDs.
Changes:
- Add an “Eden AI” provider entry to the configuration guide’s “API keys & providers” section with copy-pastable
.envand YAML examples. - Add an Eden AI example to
.env.examplealongside the existingOPENAI_API_BASEgateway note.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| examples/configuration/README.md | Adds an Eden AI provider section explaining OPENAI_API_BASE usage and the required model naming scheme. |
| .env.example | Adds a commented Eden AI OPENAI_API_BASE example and a brief note on the corresponding model format. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+239
to
+240
| which is useful for GDPR-sensitive knowledge bases. See | ||
| https://www.edenai.co/data-compliancy. |
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.
What
Documents Eden AI as a supported provider. No code change is needed: OpenKB already routes through LiteLLM's
OPENAI_API_BASEoverride, so Eden AI works today. This just documents the exact config in the configuration guide and.env.example.Eden AI is a French, EU-based OpenAI-compatible gateway. Config:
The leading
openai/selects LiteLLM's OpenAI-compatible transport (so it honorsOPENAI_API_BASE); the remaining<vendor>/<model>is Eden AI's vendor-prefixed model id.Why Eden AI (EU / GDPR / data residency)
https://api.eu.edenai.run/v3) that processes and routes prompts and outputs within the European Union (non-EU models are rejected).Useful for GDPR-sensitive knowledge bases. Refs: https://www.edenai.co/post/eu-ai-endpoint-how-to-keep-ai-requests-and-data-in-europe and https://www.edenai.co/data-compliancy
Changes
examples/configuration/README.md: an Eden AI entry in "3. API keys & providers"..env.example: an Eden AI example next to the existingOPENAI_API_BASEgateway note.Testing
litellm.completion(model=..., base_url="https://api.edenai.run/v3", api_key=...)(OpenKB's exact call path). The documented double-prefixed form returns completions for three vendors:openai/openai/gpt-4o-mini,openai/anthropic/claude-sonnet-4-5,openai/mistral/mistral-small-latest. The single-prefixedopenai/gpt-4o-minifails (LiteLLM strips the prefix), which is exactly why the docs call out the double prefix.Happy to adjust wording or move the section if you prefer.