API
Multimodal
Route text, images, audio, video and files by declared capability
Multimodal support is model- and provider-specific. Use the tenant-visible catalogue to select routes whose input and output modalities match the workload; a model name alone is not evidence of support.
Send typed content parts
Use the compatible content-part shape for text and supported media. Keep large assets in approved storage and pass only provider-supported URLs or encoded content.
- Validate MIME type and size before Router
- Do not place Router keys in asset URLs
- Apply the same data classification to attachments and text
Check route capability
Confirm input modalities, output modalities, context limit, supported parameters and regional eligibility in the catalogue before enabling a feature.
Keep product media outside Router
Router performs transient inference. It does not become a Media, Documents or Knowledge store and does not attach generated assets to product records.