diff --git a/fern/products/sdks/generators/python/configuration.mdx b/fern/products/sdks/generators/python/configuration.mdx
index ab2ed0a28..ba07e7f71 100644
--- a/fern/products/sdks/generators/python/configuration.mdx
+++ b/fern/products/sdks/generators/python/configuration.mdx
@@ -184,6 +184,25 @@ When enabled, the generated SDK omits the `X-Fern-Language`, `X-Fern-SDK-Name`,
 When enabled, the generated SDK sends a single structured `User-Agent` header of the form `{sdkName}/{version} ({os}; {arch}) {runtime}/{runtimeVersion}` (for example, `fern_examples/0.0.1 (linux; x86_64) Python/3.11.0`), carrying SDK, operating system, architecture, and runtime information in place of the default `User-Agent` and discrete platform headers. If `omit_fern_headers` is enabled, no `User-Agent` or platform headers are sent and this option has no effect.
 </ParamField>
 
+<ParamField path="allow_user_agent_app_info" type="bool" default="false" required={false} toc={true}>
+When enabled, the generated client constructor accepts `app_info: typing.Optional[typing.Dict[str, str]] = None`, with a required `name` key and optional `version` and `comment` keys. Its product token is appended to the `User-Agent` header, which lets an application built on the SDK identify itself to the API, following the [HTTP `User-Agent` grammar](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent). Also accepted as `allowUserAgentAppInfo`.
+
+```python
+client = Acme(
+    token="...",
+    app_info={"name": "partner-app", "version": "3.1.0", "comment": "+https://partner.example"},
+)
+```
+
+The token is formatted as `{name}/{version} ({comment})`, dropping `/{version}` and `({comment})` when blank, and is appended to whatever `User-Agent` the SDK would otherwise send, including the structured header from [`include_platform_headers`](#include_platform_headers) and the version resolved by [`runtime_version`](#runtime_version):
+
+```
+User-Agent: fern_examples/0.0.1 (linux; x86_64) Python/3.11.0 partner-app/3.1.0 (+https://partner.example)
+```
+
+Caller-supplied values are sanitized before they reach the header. An explicit `User-Agent` header takes precedence, the header is unchanged when no `name` is passed, and [`omit_fern_headers`](#omit_fern_headers) suppresses it entirely.
+</ParamField>
+
 <ParamField path="optional_auth" type="bool" default="false" required={false} toc={true}>
 When enabled, client auth parameters (bearer token, basic auth username and password, header auth) remain optional even when the spec's [security requirements](/learn/api-definitions/openapi/authentication) mandate auth on every endpoint, and requests are sent without an auth header when no credential is provided. By default, the client raises an error when a mandatory credential is missing. Also accepted as `optional-auth` or `optionalAuth`.
 
diff --git a/fern/products/sdks/generators/typescript/configuration.mdx b/fern/products/sdks/generators/typescript/configuration.mdx
index 1627630da..bfea7d1f6 100644
--- a/fern/products/sdks/generators/typescript/configuration.mdx
+++ b/fern/products/sdks/generators/typescript/configuration.mdx
@@ -409,6 +409,25 @@ When enabled, the generated SDK omits the `X-Fern-Language`, `X-Fern-SDK-Name`,
 When enabled, the generated SDK sends a single structured `User-Agent` header of the form `{sdkName}/{version} ({os}; {arch}) {runtime}/{runtimeVersion}` (for example, `my-sdk/0.0.1 (linux; x86_64) Node/20.11.0`), carrying SDK, operating system, architecture, and runtime information in place of the default `User-Agent` and discrete platform headers. If `omitFernHeaders` is enabled, no `User-Agent` or platform headers are sent and this option has no effect.
 </ParamField>
 
+<ParamField path="allowUserAgentAppInfo" type="boolean" default="false" toc={true}>
+When enabled, the generated client accepts an optional `appInfo` client option with a required `name` and optional `version` and `comment`. Its product token is appended to the `User-Agent` header, which lets an application built on the SDK identify itself to the API, following the [HTTP `User-Agent` grammar](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent).
+
+```typescript
+const client = new AcmeClient({
+  token: "...",
+  appInfo: { name: "partner-app", version: "3.1.0", comment: "+https://partner.example" },
+});
+```
+
+The token is formatted as `{name}/{version} ({comment})`, dropping `/{version}` and `({comment})` when blank, and is appended to whatever `User-Agent` the SDK would otherwise send, including the structured header from [`includePlatformHeaders`](#includePlatformHeaders):
+
+```
+User-Agent: @fern/simple-api/0.0.1 (linux; x86_64) Node/22.x partner-app/3.1.0 (+https://partner.example)
+```
+
+Caller-supplied values are sanitized before they reach the header. A `User-Agent` set explicitly in client or request headers takes precedence, and the header is unchanged when no `appInfo` is passed.
+</ParamField>
+
 <ParamField path="optional-auth" type="boolean" default="false" toc={true}>
 When enabled, client auth parameters (bearer token, basic auth credentials, header auth) remain optional even when the spec's [security requirements](/learn/api-definitions/openapi/authentication) mandate auth on every endpoint, and requests are sent without an auth header when no credential is provided. By default, the client throws when a mandatory credential is missing.