docs: add DaoXE OpenAI-compatible gateway example#6527
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdded a DaoXE provider section to the LLM documentation, including API key setup, OpenAI-compatible ChangesDaoXE Provider Documentation
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/edge/en/concepts/llms.mdx`:
- Around line 1291-1299: Update the DaoXE Python example around the LLM
initialization to load the .env file before reading DAOXE_API_KEY, using
load_dotenv() and its required import; alternatively, explicitly instruct users
to export the variable before running the snippet. Ensure DAOXE_API_KEY is
available when LLM is constructed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: ad8864b7-55cf-483a-9538-7ec7678d5da8
📒 Files selected for processing (1)
docs/edge/en/concepts/llms.mdx
Match neighboring provider docs: read DAOXE_API_KEY from the documented .env instead of os.getenv without load_dotenv.
CodeRabbit noted the snippet referenced a .env file without loading it. Document export (or preloaded env) and use os.getenv consistently. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Summary
Adds a DaoXE accordion to
docs/edge/en/concepts/llms.mdxnext to other gateway-style OpenAI-compatible providers.Why
CrewAI already documents custom OpenAI-compatible endpoints and providers like OpenRouter. DaoXE is a multi-model multi-protocol gateway (
https://daoxe.com/v1) that some users use as a single OpenAI-compatible base for multi-model access.Notes
custom_openai=True+base_url="https://daoxe.com/v1".edgedocs only (same pattern as neighboring provider examples).Test plan
LLM(..., custom_openai=True, base_url=...)API