Files and references

Files and references

Download Markdown ↓

A local file does not automatically become a URL an upstream service can download.

Common input formats#

Format Requirements
HTTPS URL Downloadable by the upstream and valid when read
Base64 / data URL Explicit model support and acceptable size
Multipart upload File fields supported by the endpoint and adapter

Plain text needs no object storage. Whether an image, video or audio reference requires a URL depends on its upstream API.

Use your own storage#

You can supply your own object storage or CDN URL without the platform enabling its own storage. Ensure upstream accessibility and comply with file type, size, resolution and duration limits.

Private buckets can use signed URLs. Their lifetime must cover queuing, upstream downloads and retries, not only request submission.

Platform-assisted uploads#

The platform optionally supports Aliyun OSS, Tencent Cloud COS and S3-compatible storage. Local files can become temporary download links only when the administrator has configured and enabled storage and the model's adapter supports conversion.

This is not a universal file drive. /v1/files is not currently an available general-purpose upload API. Use the upload method documented for the selected model.

When a URL cannot be read#

Check expiry, login requirements, hotlink protection and IP restrictions. localhost, 127.0.0.1, private network addresses and desktop file paths are not public reference URLs.

Treat a signed URL as a temporary access credential that may be used by the upstream. Upload only content you are authorized to use, and keep private media links and keys out of public debugging material.

Temporary media and retained results#

Platform temporary media expires and is cleaned up; it is not long-term hosting. Input references, task results and your own saved copies are separate objects. Download and archive any content you need before it expires.

Updated

Search docs