# OpenAI Compatibilioty with JNodeJS - Error **URL:** \ **Category:** Gemini API\ **Tags:** node-js\ **Created:** [November 22, 2024, 6:07am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746 "2024-11-22T06:07:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 22, 2024, 6:07am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/1 "2024-11-22T06:07:55Z")
I am experimenting with the use of OpenAI library to communicate with Gemini and follow the documentation at > **[OpenAI compatibility  |  Gemini API  |  Google AI for...](https://ai.google.dev/gemini-api/docs/openai#node.js)** When using the openai libraries on NodeJS and executing a simple await openai.models.list() I receive [generativelanguage.googleapis.com](http://generativelanguage.googleapis.com) /v1beta/openai/ 404 status code (no body) NotFoundError: 404 status code (no body) /v1beta/ 401 Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. I supply a valid gemini API key I generated for personal use. I wonder if anyone else has the same issue or has recommendations to resolve this. Thank you ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 22, 2024, 6:43am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/2 "2024-11-22T06:43:15Z")
Hi there, IIRC, the list models functionality is not available for the moment. For now, chat completions and embeddings are working. ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 22, 2024, 7:10am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/4 "2024-11-22T07:10:37Z")
> [@Hugo\_Lebegue](#): > > /v1beta/openai/ Thank you for your response. I assume that /v1beta/openai/ is the proper end point then. Regarding the streaming, is this endpoint supported? `openai.beta.chat.completions.stream(inboundS);` If not, do you have a full sample of how to use Streaming with tools (and respond to tool use) * * * On a side note, I am trying this simple code: ```auto const completion = await openai.chat.completions.create({ model: engine, user: user._id, messages: [ { role: "system", content: [{ type: "text", text: systemPrompt}] }, { role: "user", content: [{ type: "text", text:userPrompt}] }, ], temperature: 0.3, response_format: { "type": "json_object" } }) ``` And getting ` BadRequestError: 400 status code (no body)` ## Any help is appreciated Thank you for all your help ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 25, 2024, 11:18am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/6 "2024-11-25T11:18:04Z")
Hi @Hugo_Lebegue The link / resource you provided has streaming documented > **[سازگاری OpenAI  |  Gemini API  |  Google AI for Developers](https://ai.google.dev/gemini-api/docs/openai?hl=fa)** See here for working examples, constraints and roadmap of using Gemini with the OpenAI API > **[Gemini is now accessible from the OpenAI Library- Google Developers Blog](https://developers.googleblog.com/en/gemini-is-now-accessible-from-the-openai-library/)** > > Access the latest Gemini models through the OpenAI Library and REST API. Update your code with three lines and start building today. Also from there: “We will initially support the Chat Completions API and Embeddings API, with plans for additional compatibility in the weeks and months to come.” Your code sample seems to miss the actual `client` to specify the Gemini API Key and the base url. Cheers, JoKi ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 4:04am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/8 "2024-11-26T04:04:14Z")
Thank you for your feedback I have seen and read the 2 documentations links you mentioned.,I was asking the community if someone had a complete example of using tools+stream combined, specifically detailing how to respond to tool use while processing stream chunks. I realize that this is probably more a question for OpenAI. I took note that the beta section of the APIs are not supported, (for those that are still using Beta), and that the end- point for the client is created by overwriting the endpoint URL and the API key in the config section. ![image](https://d3qe71uytubmmx.cloudfront.net/original/3X/3/f/3f1991fd0d4e3fc4b93b27c1e24f503a982b07a8.png) ` const openai = new OpenAI(config)` Thank you for your help. ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 4:22am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/9 "2024-11-26T04:22:58Z")
Hello Hugo, You’re most welcome. Glad you got it working. Kindly mark a response as “solution” if it solved your issue. Thanks. ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 12:18pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/11 "2024-11-26T12:18:18Z")
Hi Jochen, Unfortunately, I can not get this end point to work . While the code works flawlessly with open AI, using the chat completion, I get a 404 No Body . If you know a way I can turn debugging on for the open ai library so I can send additional logs if this can be helpful. I am using the exact same code as the one you sent earlier. ```auto const result = await openai.chat.completions.create({ model: engine, messages: [ {"role": "system", "content": `${prompt}`}, {"role": "user", "content": `${inputText}`} ], temperature: 0.3, }) ``` I am really puzzled by this ```auto pria:middleware:openai streamConversation For user admin@praxislxp.com model gemini-1.5-flash +653ms pria:middleware:openai Connecting with config GEMINI { "apiKey": "GOCxxxxxxxxxxxxxxi1PthP6iuytt7T", "baseURL": "https://generativelanguage.googleapis.com/v1beta/openai/" } +0ms PRIA ERROR BadRequestError: 400 status code (no body) at Function.generate (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\error.js:45:20) at OpenAI.makeStatusError (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\core.js:293:33) at OpenAI.makeRequest (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\core.js:337:30) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async doStreamConversation (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\openai.js:440:28) at async Object.streamConversation (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\openai.js:385:5) at async rag.chat (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\rag.js:484:13) at async C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\ai\personal\qanda.js:90:3 { status: 400, headers: { 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'content-encoding': 'gzip', 'content-type': 'application/json; charset=UTF-8', date: 'Tue, 26 Nov 2024 12:15:57 GMT', server: 'scaffolding on HTTPServer2', 'server-timing': 'gfet4t7; dur=1951', 'transfer-encoding': 'chunked', vary: 'Origin, X-Origin, Referer', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'x-xss-protection': '0' }, request_id: undefined, error: undefined, code: undefined, param: undefined, type: undefined } ``` Let me know if you can see anything obvious. Thank you ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 1:25pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/12 "2024-11-26T13:25:02Z")
Hi @Hugo_Lebegue What’s the actual value of the model name, you are using a variable “engine” in your code? Do you use an existing model, like they are offered in Google AI Studio? Eg. something like “gemini-1.5-flash” ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 1:33pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/13 "2024-11-26T13:33:38Z")
> [@Hugo\_Lebegue](#): > > `gemini-1.5-flash` YEs, this is what I am using: gemini-1.5-flash ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 1:45pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/14 "2024-11-26T13:45:52Z")
Did you already try a plain HTTP request? Replace the {{apiKey}} variable with your key value. I’m using VS Code with REST Client extension to query the OpenAI API. This gives me an HTTP 200 response. ```auto POST https://generativelanguage.googleapis.com/v1beta/openai/chat/completions Authorization: Bearer {{apiKey}} Content-Type: application/json { "model": "gemini-1.5-flash", "messages": [ { "role": "system", "content": "You are a helpful assistant."}, { "role": "user", "content": "Explain to me how AI works"} ] } ``` (openai.http) The error response in your code says that it’s an HTTP 400 Bad Request. Meaning, there is something wrong with the data in your request sent to the OpenAI API. Are you able to debug/trace the JSON before it goes over the wire? Eventually, you are missing escaping of characters in your system message and user message? Your prompt and inputText are wrapped in single quotes only. Shouldn’t that be double-quotes and then have any double-quote in your value escaped? ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 2:46pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/15 "2024-11-26T14:46:51Z")
> [@jkirstaetter](#): > > `Bearer ` Sae problem using a simple API tester plugin from Chrome . Nothing spectacular, as if the End point is simply not listening ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 2:49pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/16 "2024-11-26T14:49:20Z")
No, in your API tester you are using the wrong URL which gives you an HTTP 404 Not Found. See my REST call regarding the actual API endpoint! ```auto https://generativelanguage.googleapis.com/v1beta/openai/chat/completions ``` ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 2:50pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/17 "2024-11-26T14:50:17Z")
Hi @Hugo_Lebegue You forgot to mask your API KEY in the screenshot! Please revoke and create a new one. ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 2:51pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/18 "2024-11-26T14:51:33Z")
> [@jkirstaetter](#): > > `chat/completions` You are correct, it worked when I corrected. This also validates my API Key (modified for posting the image here) SO Open AI is not composing the valid end poiunt URL when I specify the root as > ``` > config = { > apiKey: user?.institution?.gemini_api_key || process.env.GEMINI_API_KEY, > baseURL: `https://generativelanguage.googleapis.com/v1beta/openai/` > } > > ``` How can I trace what URL is openAI trying to get to ? ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 2:54pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/19 "2024-11-26T14:54:27Z")
That URL is correct! Because it says “baseUrl” and the actual method you are calling, like eg. `openai.chat.completions.create`, adds the remaining path to that baseUrl. But that’s not the problem. The URL seems to be correct between your code and the API tester. The problem is the data / payload your library sends as the body. This causes the HTTP 400 Bad Request because it contains information not accepted by the Gemini endpoint. ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 3:11pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/20 "2024-11-26T15:11:12Z")
I see. I use NodeJS 16, with “openai”: “^4.73.1”. I modified my locole version of core.js so I can debug code execution. This is what is now logged in the console: It is going to the right URL [https://generativelanguage.googleapis.com/v1beta/openai/chat/completions](https://generativelanguage.googleapis.com/v1beta/openai/chat/completions) The path ‘/chat/completions’ is correct. ```auto OpenAI:DEBUG:request https://generativelanguage.googleapis.com/v1beta/openai/chat/completions { method: 'post', path: '/chat/completions', body: { model: 'gemini-1.5-flash', messages: [ [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object] ], tools: [ [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object], [Object] ], n: 1, user: '65cfebc32f5e1b37d4e52327', frequency_penalty: 0, presence_penalty: 0, temperature: 0.2, stream: true, stream_options: { include_usage: true }, tool_choice: 'auto' }, stream: true } { 'content-length': '64504', accept: 'application/json', 'content-type': 'application/json', 'user-agent': 'OpenAI/JS 4.73.1', 'x-stainless-lang': 'js', 'x-stainless-package-version': '4.73.1', 'x-stainless-os': 'Windows', 'x-stainless-arch': 'x64', 'x-stainless-runtime': 'node', 'x-stainless-runtime-version': 'v16.20.2', authorization: 'Bearer xxxxxx', 'x-stainless-retry-count': '0' } OpenAI:DEBUG:response (error; (error; no more retries left)) 400 https://generativelanguage.googleapis.com/v1beta/openai/chat/completions { 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'content-encoding': 'gzip', 'content-type': 'application/json; charset=UTF-8', date: 'Tue, 26 Nov 2024 15:06:24 GMT', server: 'scaffolding on HTTPServer2', 'server-timing': 'gfet4t7; dur=374', 'transfer-encoding': 'chunked', vary: 'Origin, X-Origin, Referer', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'x-xss-protection': '0' } undefined PRIA LOGIC ERROR BadRequestError: 400 status code (no body) at Function.generate (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\error.js:45:20) at OpenAI.makeStatusError (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\core.js:293:33) at OpenAI.makeRequest (C:\_svn\_praxis\code\pria_ui\pria-ui-1\node_modules\openai\core.js:337:30) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async doStreamConversation (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\openai.js:441:28) at async Object.streamConversation (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\openai.js:386:5) at async rag.chat (C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\middlewares\rag.js:484:13) at async C:\_svn\_praxis\code\pria_ui\pria-ui-1\routes\ai\personal\qanda.js:90:3 { status: 400, headers: { 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'content-encoding': 'gzip', 'content-type': 'application/json; charset=UTF-8', date: 'Tue, 26 Nov 2024 15:06:24 GMT', server: 'scaffolding on HTTPServer2', 'server-timing': 'gfet4t7; dur=374', 'transfer-encoding': 'chunked', vary: 'Origin, X-Origin, Referer', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'x-xss-protection': '0' }, request_id: undefined, error: undefined, code: undefined, param: undefined, type: undefined } ``` Updates: I was able to make the library work until I removed from following properties the json - frequency\_penalty, - presence\_penalty, - tool\_choice, and - user Additionally, the library won’t work either if you declare more than 1 too in the tools section ```auto "tools": [ { "type": "function", "function": { "name": "get_browser", "description": "You have the 'get_browser' tool. Use 'get_browser' tool to search the web for up-to-date information ", "parameters": { "type": "object", "properties": { "argument_1": { "type": "string", "description": "The specific information, event, or topic to search (e.g. Latest financial news)." } }, "required": [ "argument_1" ] } } }, { "type": "function", "function": { "name": "get_foo", "description": "You have the 'get_foo' tool. Use 'get_foo' tool to get the users location", "parameters": { "type": "object", "properties": { "argument_2": { "type": "string", "description": "The specific location." } }, "required": [ "argument_2" ] } } } ], ``` Finally I suggest to enhance the API libs to communicate the reason for error, instead of an opaque 400. Where can we log these bugs so they get addressed in future versions of openAI lib or Gemini ? Thank you for all your help ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 4:48pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/21 "2024-11-26T16:48:36Z")
I found the problem. The issue is that the API doesn’t communicate the cause/source of the error. in the JSON sent through the APIs, It doesn’t support the following properties: - user - frequencey\_penalty - prsence\_penalty - tool\_choice Additionally, Gemini sends a 400 when I specify more than 1 tool ```auto "tools": [ { "type": "function", "function": { "name": "get_browser", "description": "You have the 'get_browser' tool. Use 'get_browser' tool to search the web for up-to-date information ", "parameters": { "type": "object", "properties": { "argument_1": { "type": "string", "description": "The specific information, event, or topic to search (e.g. Latest financial news)." } }, "required": [ "argument_1" ] } } }, { "type": "function", "function": { "name": "get_foo", "description": "You have the 'get_foo' tool. Use 'get_foo' tool to get the users location", "parameters": { "type": "object", "properties": { "argument_1": { "type": "string", "description": "The specific location." } }, "required": [ "argument_1" ] } } } ], ``` ---
**Author:** ![jkirstaetter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jkirstaetter/32/61_2.png) [@jkirstaetter](https://discuss.ai.google.dev/u/jkirstaetter)\ **Post date:** [November 26, 2024, 5:10pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/22 "2024-11-26T17:10:01Z")
Hi @Hugo_Lebegue Yes, that’s kind of described in the blog article when Google announced their beginning of OpenAI API compatibility. There are lots of things in active development right now. There are already other threads about the problem re. multiple tools not working. They just started… Dear @GUNAND_MAYANGLAMBAM please forward this to the eng. team. Thanks. As for those properties named, they are already in the types, like eg. ```auto /// /// Optional. Controls whether the model should use a tool or not, and which tool to use. /// Can be either: /// - The string \"none\", to disable tools. /// - The string \"auto\", to let the model decide. /// - The string \"required\", to force the model to use a tool. /// - A function name descriptor object, specifying the tool to use. The last option follows the following schema: { \"type\": \"function\", \"function\": {\"name\" : \"the_function_name\"} } /// public string? ToolChoice { get; set; } /// /// Optional. Presence penalty applied to the next token's logprobs if the token has already been seen in the response. /// /// /// This penalty is binary on/off and not dependant on the number of times the token is used (after the first). /// Use frequencyPenalty for a penalty that increases with each use. A positive penalty will discourage /// the use of tokens that have already been used in the response, increasing the vocabulary. A negative /// penalty will encourage the use of tokens that have already been used in the response, decreasing /// the vocabulary. /// public float? PresencePenalty { get; set; } /// /// Optional. Frequency penalty applied to the next token's logprobs, multiplied by the number of times each token has been seen in the respponse so far. /// /// /// A positive penalty will discourage the use of tokens that have already been used, proportional to the number /// of times the token has been used: The more a token is used, the more difficult it is for the model to use /// that token again increasing the vocabulary of responses. /// Caution: A negative penalty will encourage the model to reuse tokens proportional to the number of times /// the token has been used. Small negative values will reduce the vocabulary of a response. /// Larger negative values will cause the model to start repeating a common token until it hits the /// maxOutputTokens limit: "...the the the the the...". /// public float? FrequencyPenalty { get; set; } ``` Cheers, JoKi ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 26, 2024, 5:20pm UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/23 "2024-11-26T17:20:52Z")
Thank you for forwarding these findings to the Eng Team. It would be great if the API could communicate the reason for the 400. This will help save time debugging. Have a great one, and again, thank you for your help ---
**Author:** ![Hugo\_Lebegue](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/hugo_lebegue/32/30335_2.png) [@Hugo\_Lebegue](https://discuss.ai.google.dev/u/Hugo_Lebegue)\ **Post date:** [November 28, 2024, 5:44am UTC](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746/25 "2024-11-28T05:44:01Z")
Finally, using the gemini flash-1.5, you will get a 400 when - you are trying to analyze a picture that is too large (exceeds something lie 1 MB I think (not completely sure since the error code is not received) and - the file\_url can not be an actual URL, but MUST be a base 64. In Open AI you can send a standard web url, _**(Modified by moderator)**_ but for Gemini, it must be a small Base 64 I will continue to add my findings here. Thank you [Next page](https://discuss.ai.google.dev/t/openai-compatibilioty-with-jnodejs-error/50746.md?page=2)