Spring
Spring AI-specific hook for translating Embabel structured-output intent into Spring AI provider options.
Core code should not know provider payload field names such as response_format. Provider autoconfiguration modules can supply an implementation that copies and mutates their own ChatOptions subtype when the selected model supports it. This hook still routes through Spring AI option objects; it does not do direct provider tag/payload injection itself.
Parameters
native
provider/model metadata that describes which native structured-output strategy this model supports, if any.
Functions
Link copied to clipboard
abstract fun configure(options: <Error class: unknown class>, structuredOutput: StructuredOutputRequest?, nativeSupport: <Error class: unknown class>?, llm: <Error class: unknown class>?): <Error class: unknown class>