BASE URL DOCTOR

OpenAI Compatible Base URL Checker

Check for duplicates /v1, complete API path, query parameters and client automatic splicing rules. All analysis is done in the current browser only.

No API Key required Do not send a request to the target address Generate a reproducible final path
01 · Fill in the configuration

Check Base URL

The address does not leave the current browser; the tool only checks the string and concatenation.

02 · Inspection results

Waiting for address to be filled in

Fill in the Base URL currently used by other websites or projects. After checking, the recommended configuration and final request path will be displayed.

Continue to detect the real API
Troubleshooting

Determine the problem from the final request address

It doesn't matter whether the field is named "API Host", "Endpoint" or "Base URL", the key is where the client finally requested it. Open the client log or browser network panel and check the actual URL.

  1. 01

    First check if there are duplicate paths

    /v1/v1/chat/completions/chat/completions All indicate that the client and configuration have repeatedly appended paths.

  2. 02

    Look at the response type again

    Returning an HTML login page usually indicates that the request did not enter the API route; returning a JSON error continues to check authentication, models, and parameters.

  3. 03

    Make the minimum request last

    Query the model list first, and then send the short text request. After the basic call is successful, SSE, tool call and multi-modality are added.

Base URL FAQ

Tools can only verify configuration splices, actual authentication and model capabilities require actual requests.

Should the Base URL contain /v1?

Depends on whether the client automatically appends /v1. When customizing base_url directly using OpenAI SDK, it is usually filled in /v1; if the client explicitly states that it will be automatically appended, only the domain name or upper-level path is filled in. Ultimately request logs are more reliable than interface field names.

Why does /v1/v1/chat/completions appear?

The configuration value already contains /v1, and the client appends it automatically. One of the layers should be removed based on client rules and the final request address should be rechecked.

Will this tool request the API gateway I filled in?

No. The checking process only analyzes the URL string in the current browser, does not send network requests, and does not require an API Key. To verify real API responses, use model checking tools.

Why am I prompted to fill in the complete chat/completions address?

The Base URL field of most clients only accepts the base path, and the client will append models, chat/completions, or responses by itself. Filling the complete endpoint into the Base URL can easily result in duplicate paths.