LLMConsumptionType

SPI for contributing an LLMConsumption flavor to LLMConsumptionRegistry.

Implementations are discovered at runtime via java.util.ServiceLoader, so each provider must list its implementation in META-INF/services/ai.koog.agents.optimization.consumption.LLMConsumptionType. This lets the library decode any consumption flavor present on the classpath without compile-time knowledge of provider-specific types (e.g. the library never references a consumption type defined by the consuming app).

Inheritors