InvocationInput
Structured input handed to the unified invocation handler.
The plugin auto-dispatches based on the request's Content-Type and Content-Length:
application/json,text/...→ Text (UTF-8 string)multipart/...→ Multipart (MultiPartData)any other type within binaryStreamThresholdBytes → Binary (full bytes)
any other type beyond the threshold or unknown length → Stream (ByteReadChannel)
Handlers pattern-match on the variant they expect; raise an AgentCoreInvocationException for unsupported shapes.
Inheritors
Types
Request body materialised as raw bytes plus the original Content-Type.
multipart/form-data request — handler iterates over MultiPartData to read individual file/field parts (PartData.FormItem, PartData.FileItem, etc.). Useful for file uploads where metadata fields accompany binary blobs.
Request body as a ByteReadChannel for incremental reads. Use this for large uploads (audio/video/large PDF) where allocating the full payload as a ByteArray is undesirable.
Request body decoded as a UTF-8 string (used for JSON/text content types).