Base URLs and protocols
Most integration failures come from a mismatch between wire protocol, Base URL, and final endpoint, not from the model name itself.
Protocol map
| Protocol | Base URL | Representative endpoints |
|---|---|---|
| OpenAI-compatible | https://aikey365.com/v1 | /chat/completions, /responses, /embeddings, /models |
| Anthropic Messages | https://aikey365.com | /v1/messages |
| Gemini native | https://aikey365.com | /v1beta/models/{model}:generateContent |
If the console exposes a dedicated API hostname, use the current console value.
Why OpenAI clients often include /v1
Many OpenAI-compatible SDKs treat the Base URL as a version prefix and append paths such as chat/completions or responses.
Why Anthropic clients often use the root URL
Anthropic ecosystem clients commonly append /v1/messages themselves.
Gemini native
Gemini native requests use /v1beta/models/... and a different request body from OpenAI Chat Completions.
Debugging 404
Check:
- the actual protocol sent by the client,
- duplicate or missing /v1,
- automatic path concatenation,
- proxies or gateways that rewrite paths.
Changing the model will not fix an incorrect endpoint.