Skip to main content
Media Asset Management is the asset library primitive for organizing all your company’s media files — images, videos, clips, and generated content. Assets are auto-ingested when video clipping or video generation jobs complete, and can also be uploaded manually via URL or direct file upload.

CLI First

Tools

Direct file upload is available via the CLI (naive media upload --file) and the dashboard, but not as an MCP tool.

Listing Assets

The naive_media_list tool returns a paginated list of assets with optional filtering.

Filter Parameters

Uploading Assets

From URL

Direct File Upload

File uploads accept images and videos up to 100 MB. Files are stored on AWS S3 (private bucket; reads via short-lived presigned URLs).

Auto-Ingest from Jobs

When a video clipping or video generation job completes, results are automatically added to your media library:
  • Video Clipping: Each extracted clip becomes a separate asset with source_type: "video_clipping", tagged with clip and its virality score (e.g. virality:91)
  • Video Generation: The generated video is added with the prompt as the title, source_type: "video_generation", tagged with generated and the model name (e.g. text-to-video)
No manual action is needed — check your Media Asset Manager or call naive media list to see new assets. You can then create social posts directly from these assets using upload_ids on the social post API.

Updating Assets

Update title, description, or tags on any asset:

Deleting Assets

Cost

All media asset management operations are free. Storage is included with your plan. The only costs come from the upstream primitives that generate the assets (video clipping metered per finished clip and per input minute, video generation at variable cost).

Error Handling

Typical Workflow