Generation parameters and features¶
Topics: alchemy, generation, images, text
Generation-parameter models describe reusable settings independently of a particular API request. API payload models compose or adapt them where the wire contract requires different names or bounds.
Families¶
| Family | Module | Carries |
|---|---|---|
| Generic | horde_sdk.generation_parameters.generic |
shared generation concepts and constants |
| Image | horde_sdk.generation_parameters.image |
dimensions, sampling, source processing, LoRAs, control, hires fix |
| Text | horde_sdk.generation_parameters.text |
context length, output length, sampling, repetition controls |
| Alchemy | horde_sdk.generation_parameters.alchemy |
form names, upscalers, annotations, caption/interrogation types |
| Versioning | horde_sdk.generation_parameters.versioning |
compatibility metadata for evolving parameter sets |
| Templates | horde_sdk.generation_parameters.templates |
package boundary reserved for reusable parameter templates |
None generally means the caller leaves selection to the API or backend; an explicit value requests a behavior. Check
the field's Pydantic bounds and docstring because zero, empty collections, and omission are not interchangeable.
Code map¶
| Responsibility | Module | Symbol |
|---|---|---|
| Image object model | horde_sdk/generation_parameters/image/object_models.py |
ImageGenerationParameters |
| Image API payload | horde_sdk/ai_horde_api/apimodels/generate/async_.py |
ImageGenerationInputPayload |
| Text API payload | horde_sdk/ai_horde_api/apimodels/generate/text/async_.py |
ModelGenerationInputKobold |
| Alchemy names | horde_sdk/generation_parameters/alchemy/consts.py |
KNOWN_ALCHEMY_TYPES |
Parameter validation is covered under tests/generation_parameters; dispatch conversion tests verify backend-facing
representations.
Image feature sets¶
ImageGenerationFeatureFlags is shared by generation requirements and worker support advertisements. The direction is
determined by where the model is used; field names and serialized shapes remain identical. See
Dispatch normalization for subset semantics, per-baseline restrictions,
lifecycle-specific extraction, generation-feature union/intersection, and complete worker-profile union.