Provider-specific content data.
This block contains data for which there is not yet a standard type.
The purpose of this block should be to simply hold a provider-specific payload.
If a provider's non-standard output includes reasoning and tool calls, it should be
the adapter's job to parse that payload and emit the corresponding standard
ReasoningContentBlock and ToolCalls.
Has no extras field, as provider-specific data should be included in the
value field.
create_non_standard_block may also be used as a factory to create a
NonStandardContentBlock. Benefits include:
NonStandardContentBlock()Type of the content block. Used for discrimination.
Unique identifier for this content block.
Either:
UUID4 prefixed with 'lc_'))Provider-specific content data.
Index of block in aggregate response. Used during streaming.