Authenticate and submit the job
Send a single request with your API key, generation parameters, and optional webhook target. The API is structured for products that need predictable request flow rather than one-off demos.
API
Build media generation, editing, and enhancement directly into your product.
The LeronX API is designed for teams that want a cleaner way to add AI video workflows into apps, internal tools, creative systems, or automated pipelines without stitching together a fragile media stack.
Usage-based API pricing
Async jobs with polling or webhook delivery
Built for product teams, internal tools, and automation
Integration Flow
Structured for products that need a predictable media pipeline.
The API is meant to sit inside real systems. That means submission, job tracking, and downstream delivery should feel readable for engineering teams and product operators alike.
Track progress cleanly
Handle jobs through polling or webhook callbacks depending on your product architecture. That keeps generation, editing, and enhancement flows easy to orchestrate inside larger pipelines.
Deliver or chain the result
Once the asset is ready, route it into your product, moderation layer, review queue, or next media task. The API is meant to fit real workflow chains, not live in isolation.
Capabilities
Choose the media surface that fits the job instead of forcing every request through one route.
The explorer below keeps the category readable: pick a capability, see what it is good for, and inspect the shape of the request and response without leaving the page.
High-energy video generation
Dynamic Motion API
Use the Dynamic Motion API when a plain generation pass is not enough and the scene needs movement that feels pushed, directional, and visually intentional.
What this route is good for
- Optimized for scenes where camera movement matters as much as the prompt itself.
- Fits products that need more dramatic motion than a standard baseline generation route.
- Works well for launch content, branded motion, and richer visual storytelling passes.
Request Example
curl --request POST "$LXR_API_BASE/v1/video/dynamic-motion" \
--header "Authorization: Bearer your_api_key" \
--header "Content-Type: application/json" \
--data '{
"prompt": "A sleek running shoe bursts through a cloud of colored powder, camera tracking low and forward, sharp lighting, high-energy motion, cinematic sports commercial style.",
"aspect_ratio": "16:9",
"duration": "5s",
"quality": "1080p"
}'
Response Shape
{
"id": "job_dyn_82f91",
"status": "queued",
"type": "dynamic_motion",
"poll_url": "/v1/jobs/job_dyn_82f91"
}
API Pricing
Readable pricing for generation, enhancement, and audio workflows.
This structure is meant to help teams estimate cost early, compare quality paths, and decide where fast lanes or premium routes make the most sense inside a product.
Usage-based from the start
Billing is shaped around the work being done: generation, enhancement, and audio, rather than seat-count math or forced bundle tiers.
Readable cost structure
The table layout is meant to help teams estimate output cost early, compare paths, and decide where to use fast lanes versus premium quality.
Custom volume is still available
If your product needs heavier throughput, procurement-friendly billing, or longer planning windows, the API team can shape a larger agreement with you.
Video generation
Core generation pricing for direct video creation and edit-oriented passes.
| Generation model | LeronX 2.0 | LeronX 2.0 Fast |
|---|---|---|
| Base generation cost | $0.0066 / million pixels | $0.0023 / million pixels |
| Edit / modify cost | $0.0161 / million pixels | $0.0056 / million pixels |
Video upscaling
Resolution upgrade pricing for polish passes and higher-fidelity delivery.
| Upscaling path | Output 720p | Output 1080p | Output 4K |
|---|---|---|---|
| From 540p | $0.06 / sec | $0.10 / sec | $0.12 / sec |
| From 720p | — | $0.04 / sec | $0.05 / sec |
| From 1080p | — | — | $0.03 / sec |
Audio generation
Simple usage pricing for audio output inside media workflows.
| Audio path | Rate |
|---|---|
| Per second | $0.021 / sec |
Estimated output cost for 16:9 video without audio
Illustrative cost snapshots for common durations and resolutions.
| Format | LeronX 2.0 | LeronX 2.0 Fast |
|---|---|---|
| 540p · 5 sec | $0.42 | $0.15 |
| 540p · 9 sec | $0.74 | $0.26 |
| 720p · 5 sec | $0.73 | $0.25 |
| 720p · 5 sec (edit) | $1.79 | $0.62 |
| 720p · 9 sec | $1.31 | $0.46 |
| 1080p · 5 sec | $0.89 | $0.41 |
| 1080p · 9 sec | $1.58 | $0.74 |
| 4K · 5 sec | $0.99 | $0.52 |
| 4K · 9 sec | $1.76 | $0.92 |
If your product needs a higher-volume agreement, planned throughput, or custom commercial terms, contact us at support@leronx.org.
FAQ
Questions teams usually ask before integrating.
If you are evaluating fit, these are the fastest answers to the operational questions that usually come up first.
The API is structured around async jobs. You can poll job state directly or provide a webhook URL so your product gets notified when media is ready.
No. The current page covers more than base generation: dynamic motion, editing, rendering, image-to-video, upscaling, and audio-related pricing paths are all part of the API story.
Billing is usage-based. Different tasks price differently, so teams can choose faster or higher-fidelity routes intentionally instead of paying one flat rate for everything.
Yes. If your product starts with a modest integration and grows into heavier usage, we can move the conversation toward volume planning, procurement support, and custom commercial terms.
Founders, product teams, agencies, and internal platform teams are all welcome. If you are figuring out fit, email us at support@leronx.org and we will help you map the right route.
Next Step
If your product needs AI media as infrastructure, we can help you shape the right route.
Whether you are building a creator product, an internal workflow tool, or a client-facing media feature, we can talk through fit, usage patterns, and the cleanest integration path.
