init_kwargs_factory

Optional factory producing dynamic init kwargs at resolution time.

Use when values depend on runtime state such as environment variables.

Within a single profile, whenever the factory and init_kwargs set the same key, the factory's value wins. For example:

ProviderProfile(
    init_kwargs={"temperature": 0, "timeout": 30},
    init_kwargs_factory=lambda: {"temperature": 0.7, "base_url": os.environ["BASE_URL"]},
)

At resolution, this forwards temperature=0.7 (factory wins), timeout=30 (only in static), and base_url=<env value> (only from factory) to init_chat_model.

When merging profiles, if both the base and override profiles define a factory, both run at every resolution — base first, then override — and their outputs merge with the override's values winning on any shared keys. A worked example: the built-in OpenRouter factory always sets app_url and app_title; layer a user profile whose factory reads a per-tenant OPENROUTER_APP_TITLE_TENANT env var and sets app_title from it. Every resolution runs both factories; the user's app_title replaces the built-in, while the built-in's app_url is preserved.