diff --git a/docs/core-concepts/structured-output.md b/docs/core-concepts/structured-output.md
index 12a649d..74d28ed 100644
--- a/docs/core-concepts/structured-output.md
+++ b/docs/core-concepts/structured-output.md
@@ -114,6 +114,9 @@ Structured output supports all the same options as text generation, including:
 - Message history
 - Tools and function calling
 - System prompts
+- withClientOptions
+- withClientRetry
+- usingProviderConfig
 
 See the [Text Generation](./text-generation.md) documentation for details on these common settings.
 
diff --git a/docs/core-concepts/text-generation.md b/docs/core-concepts/text-generation.md
index 9ed5545..539016d 100644
--- a/docs/core-concepts/text-generation.md
+++ b/docs/core-concepts/text-generation.md
@@ -137,6 +137,10 @@ Under the hood we use Laravel's [HTTP client](https://laravel.com/docs/11.x/http
 
 Under the hood we use Laravel's [HTTP client](https://laravel.com/docs/11.x/http-client#main-content). You can use this method to set [retries](https://laravel.com/docs/11.x/http-client#retries) e.g. `->withClientRetry(3, 100)`.
 
+`usingClientConfig`
+
+This allows for complete or partial override of the providers configuration. This is great for multi-tenant applications where users supply their own API keys. These values are merged with the original configuration allowing for partial or complete config override.
+
 ## Response Handling
 
 The response object provides rich access to the generation results: