open-compass / open-compass/VLMEvalKit

OpenAI-compat: GPT4V api_base is the full /v1/chat/completions URL, not /v1

Open
#1,661 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.4k
Forks
768
Avg merge
1d 10h
Merged PRs (30d)
17

Description

Working config (GPT4V, api_base is the full chat URL)

VLMEvalKit GPT4V / OpenAIWrapper posts api_base as-is (requests.post(self.api_base, ...)). A Chat Completions host whose public catalog is GET https://api.pzero.studio/v1/models (no key) fits if that field is the full chat URL.

export OPENAI_API_KEY=<Bearer key for that host>
export OPENAI_API_BASE=https://api.pzero.studio/v1/chat/completions

Or a --config model slot:

{
  "class": "GPT4V",
  "model": "kimi-k2-6",
  "api_base": "https://api.pzero.studio/v1/chat/completions"
}

A /v1 root 404s (the wrapper does not append /chat/completions). Do not use use_azure=True. Do not pass the built-in GPT4o row (hardcoded gpt-4o-*). model is a catalog id with vision. Names containing o1, o3, o4, or gpt-5 swap in max_completion_tokens.

Not asking for a first-party provider. GPT4V plus that api_base is enough.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the GPT4V/OpenAIWrapper implementation and its requests.post(self.api_base, ...) call. Compare the documented configuration with the current behavior, then verify the supplied /v1/chat/completions endpoint and model settings; completion requires a clearly defined fix or documentation update.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.