deploy: b5ebb1beea

includes/llms.txt

@@ -1,6 +1,6 @@
 Plano Docs v0.4.22
 llms.txt (auto-generated)
-Generated (UTC): 2026-06-03T17:10:24.816770+00:00
+Generated (UTC): 2026-06-03T20:39:15.011041+00:00
 
 Table of contents
 - Agents (concepts/agents)
@@ -6960,6 +6960,28 @@ The following is a complete reference of the plano_config.yml that controls the
 the Plano gateway. This where you enable capabilities like routing to upstream LLm providers, defining prompt_targets
 where prompts get routed to, apply guardrails, and enable critical agent observability features.
 
+Model provider headers
+
+Each entry under model_providers (or the legacy llm_providers alias) may include a headers map of extra
+HTTP headers that Plano adds to upstream LLM requests. Plano applies these headers after it sets authentication from
+access_key or passthrough_auth, so you can supply provider-specific metadata without replacing the configured
+credentials.
+
+Type: map of strings (header name → value)
+
+Optional: yes
+
+Common uses: required User-Agent values, organization or account identifiers, or other headers some APIs expect
+
+model_providers:
+  - model: moonshotai/kimi-for-coding
+    access_key: $MOONSHOTAI_API_KEY
+    base_url: https://api.kimi.com/coding/v1
+    headers:
+      User-Agent: "KimiCLI/1.3"
+
+The example below includes this and other provider options in context.
+
 Plano Configuration - Full Reference
 
 # Plano Gateway configuration version
@@ -7011,6 +7033,14 @@ model_providers:
     http_host: api.custom-provider.com
     access_key: $CUSTOM_API_KEY
 
+  # headers: optional map of extra HTTP headers sent on upstream requests (after auth).
+  # Use for provider-specific requirements such as User-Agent, org IDs, or account headers.
+  - model: moonshotai/kimi-for-coding
+    access_key: $MOONSHOTAI_API_KEY
+    base_url: https://api.kimi.com/coding/v1
+    headers:
+      User-Agent: "KimiCLI/1.3"
+
 # Model aliases - use friendly names instead of full provider model names
 model_aliases:
   fast-llm: