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.
api.video is infrastructure for hosting, managing, delivering, and live-streaming video, with AI transcription and summaries. Rendley composes and renders edits: an in-browser SDK, a REST API, and an MCP server. They solve different problems and can work together.
api.video is video hosting and delivery infrastructure: fast encoding, VOD and live streaming, a player, and a global delivery network, plus AI transcription and summaries. Rendley is a compositional editor and render engine. They are adjacent, not head-to-head. Edit and render in Rendley, then host and stream through api.video.
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.
The core distinction. api.video ingests, encodes, and streams your video. Rendley builds the edit and renders the output. Different jobs in the pipeline.
api.video’s delivery network and player are a real strength. Rendley focuses on producing the finished file rather than streaming it.
Rendley’s REST API and hosted MCP server are built for editing and rendering. api.video’s API is built for ingest, hosting, and delivery.
Rendley aggregates 25+ generation models inside a project. api.video’s AI is centered on transcription and summarization of hosted content.
| Rendley Studio | api.video | |
|---|---|---|
| Primary use case | Compositional video editing and rendering | Video hosting, management, delivery, and live streaming |
| In-browser editing SDK | Yes — @rendley/sdk renders client-side (WebCodecs/WebGL) | No editing SDK; upload/streaming SDKs (Node, Python, …) |
| Timeline composition | Yes — layers, transitions, effects, audio, captions | No — hosting and streaming, not multi-clip editing |
| Hosting and live streaming | Exports via signed URLs; not a streaming host | Yes — VOD + live, player, 140+ PoP delivery |
| Official MCP server | Yes — hosted, 18 tools | No editing MCP server |
| AI features | 25+ generation models + capability actions | Transcription and summarization |
| Object storage region | EU — Hetzner, Nuremberg (Germany) | Check vendor docs |
| Pricing model | Plans + credits: Free, $15, $30, $70/mo (1 credit = $0.01) | Pay-as-you-go per minute: storage $2.85/1,000 min, delivery $1.70/1,000 min, transcription $0.10/min; free sandbox |
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.