One stable API
Use a single contract while provider routing and model details stay behind the platform boundary.
Route image and video generation through one key, one balance and stable branded model IDs—without exposing provider complexity to your product.
import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.MODELLANE_API_KEY,
baseURL: "https://api.usemodellane.com/v1",
});
const image = await client.images.generate({
model: "modellane-fast-image",
prompt: "Editorial product photograph",
size: "1024x1024",
});
console.log(image.data[0].url);The control plane
The platform handles authentication, model routing, job state, delivery and usage records so your team can focus on the product.
Use a single contract while provider routing and model details stay behind the platform boundary.
Keep familiar JavaScript and Python SDK workflows for image generation requests.
Know the published fixed price before submission. Failed generations are not charged.
Follow queued, processing, completed and failed states from request to final asset.
Outputs are copied to private storage and delivered through short-lived signed URLs.
Receive signed completion and failure events without building a polling loop for every job.
Built for developers
Start with the synchronous image endpoint today. Use the same job system for live tracking and long-running generation workflows.
curl https://api.usemodellane.com/v1/images/generations \
-H "Authorization: Bearer $MODELLANE_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: launch-campaign-01" \
-d '{
"model": "modellane-fast-image",
"prompt": "A premium studio product photo",
"size": "1024x1024"
}'{
"created": 1784987423,
"data": [{ "url": "https://api.usemodellane.com/v1/generations/..." }]
}From key to asset
A small public surface keeps integration clear while the platform handles provider mapping and delivery behind the scenes.
Issue a scoped API key from your workspace and reveal its secret once.
Call the branded model ID with the OpenAI SDK or a plain HTTP request.
Track the job live, then use or download the private result while it is available.
Private by default
Designed for production traffic
Security and delivery
Keys belong to projects. Output files remain in private storage. Signed links expire quickly, while generation metadata stays available for operational visibility.
Minimal retention
Prompts are not written to permanent application logs.
Media isolation
Provider output URLs are never returned directly.
Create a project key, choose the published model and test the complete request lifecycle from the dashboard.