From ba4cc01408d4aab690a8ac1f5afd053c3c39489f Mon Sep 17 00:00:00 2001 From: Sylvester Kaczmarek <16242628+sylvesterkaczmarek@users.noreply.github.com> Date: Tue, 18 Aug 2026 23:48:27 +0100 Subject: [PATCH 1/2] docs: correct client rate-limit guidance --- .../src/main/kotlin/com/openai/client/OpenAIClient.kt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClient.kt b/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClient.kt index d2352b66f..491c0dcbd 100644 --- a/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClient.kt +++ b/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClient.kt @@ -35,9 +35,9 @@ import java.util.function.Consumer * * This client performs best when you create a single instance and reuse it for all interactions * with the REST API. This is because each client holds its own connection pool and thread pools. - * Reusing connections and threads reduces latency and saves memory. The client also handles rate - * limiting per client. This means that creating and using multiple instances at the same time will - * not respect rate limits. + * Reusing connections and threads reduces latency and saves memory. Requests may be retried + * individually when the API returns a retryable response, but the client does not proactively + * coordinate API rate limits across requests or client instances. * * The threads and connections that are held will be released automatically if they remain idle. But * if you are writing an application that needs to aggressively release unused resources, then you From ea781b33c78a5a8859b144ab476ed7926c44fb9e Mon Sep 17 00:00:00 2001 From: Sylvester Kaczmarek <16242628+sylvesterkaczmarek@users.noreply.github.com> Date: Tue, 18 Aug 2026 23:48:47 +0100 Subject: [PATCH 2/2] docs: correct async client rate-limit guidance --- .../src/main/kotlin/com/openai/client/OpenAIClientAsync.kt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClientAsync.kt b/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClientAsync.kt index d4fb531ee..53ab3176e 100644 --- a/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClientAsync.kt +++ b/openai-java-core/src/main/kotlin/com/openai/client/OpenAIClientAsync.kt @@ -35,9 +35,9 @@ import java.util.function.Consumer * * This client performs best when you create a single instance and reuse it for all interactions * with the REST API. This is because each client holds its own connection pool and thread pools. - * Reusing connections and threads reduces latency and saves memory. The client also handles rate - * limiting per client. This means that creating and using multiple instances at the same time will - * not respect rate limits. + * Reusing connections and threads reduces latency and saves memory. Requests may be retried + * individually when the API returns a retryable response, but the client does not proactively + * coordinate API rate limits across requests or client instances. * * The threads and connections that are held will be released automatically if they remain idle. But * if you are writing an application that needs to aggressively release unused resources, then you