OpenAI-compat: gen_api_answer.py --openai-api-base /v1, not the API server
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Review fastchat/llm_judge/gen_api_answer.py alongside docs/openai_api.md to distinguish the consumer configuration from the API server setup. Verify the documented command uses a remote /v1 base, a catalog model id, and no embeddings; done means the documentation clearly reflects this workflow without requiring a controller or worker.
Written by the indexing model from the issue text.
Description
Working config (gen_api_answer.py --openai-api-base /v1)
The consumer path is fastchat/llm_judge/gen_api_answer.py. --openai-api-base sets legacy openai.api_base to the /v1 root. That is the OpenAI-compatible join for answering against a remote Chat Completions host.
docs/openai_api.md is the server (fastchat.serve.openai_api_server). Do not start a controller or worker to talk to a hosted /v1. Override default gpt-3.5-turbo with a catalog id.
A Chat Completions host whose public catalog is GET https://api.pzero.studio/v1/models (no key) fits --openai-api-base if the value is https://api.pzero.studio/v1.
export OPENAI_API_KEY=<Bearer key for that host>
python gen_api_answer.py \
--model deepseek-v4-flash \
--openai-api-base https://api.pzero.studio/v1
Keep embeddings off this host.
- Dominant language
- Python
- Stars
- 39.5k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from lm-sys/FastChat
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100