Skip to content

Kling: Video v3.0 Standard provider comparison

kwaivgi/kling-v3.0-std

Kling v3.0 Standard is a video generation model from Kuaishou. It supports text-to-video and image-to-video workflows, with first-frame and last-frame control for guided scene composition. Clips range from 3 to...

Endpoints:
1
Context:
0
Input:
text, image
Output:
video

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per second for duration seconds. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Video prices use OpenRouter’s dedicated pricing SKUs, including resolution-specific per-second units. Missing speed data never removes an endpoint.

Endpoint comparison for Kling: Video v3.0 Standard
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
AtlasCloudatlas-cloud
Current pricing
  • $0.084 per second (duration seconds)
  • $0.126 per second (duration seconds with audio)
  • $0.084 per second (text to video duration seconds 480p)
  • $0.084 per second (text to video duration seconds 720p)
  • $0.084 per second (image to video duration seconds 720p)
  • $0.084 per second (text to video duration seconds 1080p)
  • $0.084 per second (image to video duration seconds 1080p)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
Insufficient recent data
Context
0
Model format
unknown
Max output
N/a
3 parameters

max_tokens, temperature, top_p

Endpoint data fetched .

Video v3.0 Standard deployment guide

How to choose a Video v3.0 Standard inference provider

Video v3.0 Standard is indexed here as a video model by Kling, with 1 provider endpoint from AtlasCloud. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 0-token context window. It accepts text, image input and returns video output. 3 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare video billing units directly

At least one second is published consistently across the listed endpoints, allowing a direct price chart for duration seconds. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

Published endpoint formats include unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.