AI Video Generation: API Integration & Self-Hosted Solutions

AI Video Generation: API Integration & Self-Hosted Solutions

A studio requested automatic creation of 10-second ad clips from product photos. Previously, designers edited manually — 2 clips per day. We integrated Kling 1.5 and Runway Gen-3 APIs, added a priority queue and post-processing. Throughput increased to 50 clips per day. This is a typical case: AI video generation from text or image prompts is no longer a toy but a working tool for marketing, production, gamedev, and education.

What Problems We Solve

• Unstable quality: different prompts yield different results. Our integration with Kling 1.5 allows specifying negative prompts, CFG scale, and pro mode for better control. For Runway, we pick a 1280:768 aspect ratio and 10-second duration — enough for short ads. Kling 1.5 offers 30% more control over Runway via negative prompts and cfg_scale.
• Generation latency: cloud API wait times can reach 5 minutes. We build async pipelines with WebSocket notifications and Redis queues. In a self-hosted setup (CogVideoX on A100), latency drops to 2 minutes for a 6-second clip.
• Cost at scale: each Kling request costs ~$0.10. At 5,000 clips/month, that's $500. Self-hosted CogVideoX is 2–3x cheaper than cloud APIs for large volumes — if traffic exceeds 10,000 requests/month, we recommend switching to your own GPUs, which can yield monthly savings of $800–$1,000.

Integrating Kling API

For one marketplace, we implemented text-to-video and image-to-video via Kling. Python code with httpx.AsyncClient and asyncio handles up to 100 parallel requests. Example KlingVideoGenerator class below.

import httpx
import asyncio
import json

class KlingVideoGenerator:
    def __init__(self, api_key: str):
        self.api_key = api_key
        self.base_url = "https://api.klingai.com/v1"

    async def text_to_video(
        self,
        prompt: str,
        negative_prompt: str = "",
        duration: int = 5,  # 5 or 10 seconds
        aspect_ratio: str = "16:9",  # 16:9, 9:16, 1:1
        mode: str = "std",  # std (faster) or pro (quality)
        cfg_scale: float = 0.5
    ) -> str:
        """Create generation task, return task_id"""
        async with httpx.AsyncClient() as client:
            resp = await client.post(
                f"{self.base_url}/videos/text2video",
                headers={"Authorization": f"Bearer {self.api_key}"},
                json={
                    "prompt": prompt,
                    "negative_prompt": negative_prompt,
                    "cfg_scale": cfg_scale,
                    "mode": mode,
                    "duration": str(duration),
                    "aspect_ratio": aspect_ratio
                }
            )
            return resp.json()["data"]["task_id"]

    async def image_to_video(
        self,
        image_url: str,
        prompt: str = "",
        duration: int = 5,
        motion_intensity: float = 0.5
    ) -> str:
        async with httpx.AsyncClient() as client:
            resp = await client.post(
                f"{self.base_url}/videos/image2video",
                headers={"Authorization": f"Bearer {self.api_key}"},
                json={
                    "image_url": image_url,
                    "prompt": prompt,
                    "duration": str(duration),
                    "cfg_scale": motion_intensity
                }
            )
            return resp.json()["data"]["task_id"]

    async def wait_for_result(self, task_id: str, timeout: int = 300) -> str:
        """Poll until done, return video URL"""
        async with httpx.AsyncClient() as client:
            for _ in range(timeout // 5):
                await asyncio.sleep(5)
                resp = await client.get(
                    f"{self.base_url}/videos/text2video/{task_id}",
                    headers={"Authorization": f"Bearer {self.api_key}"}
                )
                data = resp.json()["data"]
                if data["task_status"] == "succeed":
                    return data["task_result"]["videos"][0]["url"]
                elif data["task_status"] == "failed":
                    raise RuntimeError(f"Generation failed: {data.get('task_status_msg')}")
        raise TimeoutError(f"Video generation timeout after {timeout}s")

Similarly, Runway Gen-3 is integrated. The difference is in the response format and support for image-to-video with prompt_image.

Why Choose Self-Hosted CogVideoX?

Note: when the monthly generation volume exceeds 10,000 minutes, cloud APIs become more expensive than a GPU server. CogVideoX-5b on A100 (80 GB) generates 49 frames in 2 minutes — ~6 seconds of video at 8 FPS. Resolution is 720p, but quality approaches Kling. You have full pipeline control, can fine-tune on your own data (LoRA), and pay no per-request fees.

from diffusers import CogVideoXPipeline
import torch

pipe = CogVideoXPipeline.from_pretrained(
    "THUDM/CogVideoX-5b",
    torch_dtype=torch.bfloat16
)
pipe.enable_model_cpu_offload()
pipe.vae.enable_tiling()

def generate_video_local(
    prompt: str,
    num_frames: int = 49,  # ~6 sec at 8 fps
    guidance_scale: float = 6.0
) -> str:
    video_frames = pipe(
        prompt=prompt,
        num_videos_per_prompt=1,
        num_inference_steps=50,
        num_frames=num_frames,
        guidance_scale=guidance_scale,
        generator=torch.Generator("cpu").manual_seed(42)
    ).frames[0]

    output_path = "/tmp/output_video.mp4"
    from diffusers.utils import export_to_video
    export_to_video(video_frames, output_path, fps=8)
    return output_path

How We Structure the Development Process?

1. Analytics and model selection — test Kling, Runway, Sora (if available), CogVideoX on your data. Collect p99 latency and cost metrics.
2. Architecture design — decide on pattern: API-only (fast) or self-hosted (cheap at scale). Document the scheme.
3. Integration implementation — write async clients, queue handlers, S3 storage. For self-hosted, deploy with Triton Inference Server and ONNX Runtime for acceleration.
4. Testing — A/B compare with manual editing. Measure FID/CLIP and subjective quality.
5. Deployment and monitoring — set up CI/CD, logging in Loki, alerts in Telegram.

Estimated Timelines

• Single API integration (Kling/Runway): 3 to 5 days.
• Platform with multiple providers, queue, and storage: 3 to 4 weeks.
• Self-hosted CogVideoX + optimization: 4 to 6 weeks.

What's Included in the Work

• API and architecture documentation
• Access to the code repository
• Team training (2–3 sessions)
• 3-month warranty on the integration
• Support during launch (first 2 weeks)

Platform Comparison

Applications by Niche

We have over 10 years of experience in AI and machine learning, having completed 50+ integration projects for video generation pipelines. Our team specializes in MLOps and API orchestration, ensuring reliable and scalable solutions. If you need AI video generation, contact us — we'll evaluate your project in 2 days and propose the optimal solution. Order a pilot project to see it in action.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Video Generation: Which Models Are Best?

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

• Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
• Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
• Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
• Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

• Model (or API integration) with performance benchmarks (latency p99, throughput).
• Pipeline documentation (prompt engineering guide, model card, dependency versions).
• Integration with your backend (REST/gRPC, queues).
• Configured monitoring (dashboards, alerts for quality drift).
• Training workshop for the team (2–4 hours).
• Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.