[FEATURE] Document Nebius Serverless Endpoints in the LLM guide
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 58.8k
- Forks
- 8.5k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 109
Description
Feature Area
Documentation
Is your feature request related to a an existing bug? Please link it here.
N/A
Describe the solution you'd like
The LLM guide documents Nebius AI Studio / Token Factory, but users running their own model on a Nebius Serverless Endpoint need different configuration: the endpoint URL, its bearer token, and the exact served model ID.
I’ve prepared a documentation change using CrewAI’s existing custom_openai=True support. It adds:
- Endpoint configuration and authentication instructions.
- A small Agent/Task/Crew example with a local arithmetic tool.
- Model and vLLM tool-calling prerequisites.
- Readiness, streaming, troubleshooting and cleanup guidance.
- Matching English, Arabic, Korean and Brazilian Portuguese sections.
The example links to the existing vLLM deployment guide for Nebius Serverless. No runtime changes or new dependencies are needed.
Describe alternatives you've considered
No response
Additional context
No response
Willingness to Contribute
Yes, I'd be happy to submit a pull request
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the LLM guide’s existing Nebius AI Studio / Token Factory documentation and the project’s custom_openai=True support. Use the linked vLLM deployment guide for Nebius Serverless as the external reference, then verify the English, Arabic, Korean, and Brazilian Portuguese sections cover configuration, authentication, prerequisites, readiness, streaming, troubleshooting, and cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100