npm i @rendley/sdk import { Engine } from '@rendley/sdk'const engine = await Engine.create()await engine.addClip('intro.mp4')await engine.export() // WebCodecs
A real editing engine that renders in the browser.
JSON2Video renders a video from a JSON movie schema, billed per second of output. Rendley gives you that render API plus a real in-browser editing engine and a hosted MCP server, so your users can edit in the browser and your backend can render — from one platform.
JSON2Video is a lean, JSON-driven render API with cheap per-second billing and non-expiring credits, a good fit for templated social and marketing clips. Rendley covers the same render-from-JSON job through a deterministic edit spec, then adds two surfaces JSON2Video does not have: an in-browser @rendley/sdk editing engine and an official hosted MCP server.
npm i @rendley/sdk import { Engine } from '@rendley/sdk'const engine = await Engine.create()await engine.addClip('intro.mp4')await engine.export() // WebCodecs
A real editing engine that renders in the browser.
curl api.rendley.com/v1/agent/sessions \ -H "Authorization: Bearer $KEY" \ -d '{ "prompt": "30s launch promo" }' # poll the job, then pull a signed URL
Prompt to video from one deterministic endpoint.
# mcp.rendley.com — Apache-2.0claude mcp add rendley \ https://mcp.rendley.com "Cut a 15s teaser from these clips"
Hosted server, 18 tools, open source.
JSON2Video is a render-only service: you POST a JSON movie and get a file back. Rendley returns a file too, but the same engine also runs live inside the browser as an editor.
Both let you describe a video as structured data. JSON2Video centers everything on its movie schema and templates; Rendley pairs a deterministic edit spec with project CRUD and asset uploads.
JSON2Video has no MCP server. Rendley ships an official hosted one plus a prompt-to-video agent endpoint, so an LLM can drive real edits, not just fill a template.
Both support 4K and can pull in generated media. Rendley aggregates 25+ models across vendors with a matching cost endpoint per call.
| Rendley Studio | JSON2Video | |
|---|---|---|
| In-browser editing SDK | Yes — @rendley/sdk renders client-side (WebCodecs/WebGL) | No — thin SDK wrappers over the HTTP render API |
| Render REST API | Yes — api.rendley.com/v1, OpenAPI, jobs + signed URLs | Yes — POST a JSON movie schema, get a rendered file |
| Official MCP server | Yes — hosted, 18 tools | No |
| Prompt-to-video agent | Yes — /agent/sessions endpoint | No — template + element driven |
| AI generation models | 25+ aggregated (Veo, Kling, Seedance, Sora, Flux, DALL-E…) | TTS + AI element integrations |
| Max export resolution | 4K target (Pro and Business plans) | 4K (billed at 4× the per-second credit rate) |
| Free tier | Free plan (720p, watermark) | 600 non-expiring credits, but watermarked |
| Object storage region | EU — Hetzner, Nuremberg (Germany) | Check vendor docs |
| Pricing model | Plans + credits: Free, $15, $30, $70/mo (1 credit = $0.01) | Per-second credits: subs from $19.95/mo; packs $49.95–$199.95 |
Competitor details are from public pricing and documentation and can change. Verify current specifics on the vendor’s own site.
Generate clips, images, and voiceovers without leaving the editor. New models are added as they launch.
Free to start, with no length caps. Try it on a real project.