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.
Build on a deeper developer surface than VEED’s editor-derived API
VEED exposes an AI video API for generation, lip sync, and editing endpoints, derived from its consumer editor. Rendley is developer-first: an in-browser editing SDK, a REST API, and a hosted MCP server, all built on the same engine.
Unlimited exportsFree planBrowser-based
VEED API surfaces AI video endpoints (generation, lip sync, editing) from VEED’s consumer editor. It overlaps with Rendley on AI and editing endpoints, but is derived from a consumer product, with no confirmed in-browser SDK or MCP server. Rendley is developer-first across three surfaces: an in-browser editing engine, a REST API, and a hosted MCP server.
One platform, three surfaces
Everything ships in code.
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.
3
Surfaces in one platform: SDK, API, MCP
25+
AI models built in, added as they launch
18
Tools in the hosted MCP server
EU
Assets stored in Germany (Hetzner)
How they compare
Where Rendley Studio pulls ahead.
Developer-first SDK vs editor-derived endpoints
Rendley’s SDK is a real in-browser editing engine that developers embed. VEED’s API exposes endpoints derived from its consumer editor, without a confirmed in-browser SDK.
Rendley Studio
- @rendley/sdk is a JS/TS editing engine that runs completely in the browser
- Renders client-side with WebCodecs and WebGL, with an FFmpeg (WASM) fallback
- Published on npm; it is the same engine that powers the Rendley app
- Embed a full editor UI or drive the engine headlessly
VEED API
- AI video API exposed from the VEED consumer editor
- Generation, lip sync, and editing endpoints
- No confirmed in-browser editing SDK
The render API
Both expose an API. Rendley’s REST API covers uploads, editing, exports, jobs, and a prompt-to-video agent with a deterministic edit spec.
Rendley Studio
- REST API at api.rendley.com/v1 with an OpenAPI schema
- Uploads, project edits, /export plus /export/cost, and job polling to a signed URL
- Prompt-to-video agent at /agent/sessions; deterministic edit spec
- Same engine callable from the SDK, HTTP, and MCP
VEED API
- AI generation, lip sync, and editing endpoints
- Derived from the consumer editor rather than a documented edit spec
- Pricing not published on the API page (contact/usage-based)
MCP and agents
Rendley ships an official hosted MCP server so agents can drive editing directly. VEED has no confirmed MCP server.
Rendley Studio
- Hosted MCP server at mcp.rendley.com with 18 tools
- Works with Claude, ChatGPT, Cursor, Codex, and any remote-MCP client
- Drives the hosted editor and API; requires a paid plan
- Open source (Apache-2.0): rendleyhq/rendley-mcp
VEED API
- No confirmed official MCP server
- AI capabilities exposed through its API endpoints
AI generation models
Both lean into AI. Rendley aggregates 25+ models from many vendors inside one project with per-call cost endpoints.
Rendley Studio
- 25+ models across video, image, voice, music, and translation
- Video: Veo, Kling, Seedance, Sora, Wan, Hailuo; image: Flux, DALL-E, Nano Banana, Imagen
- Voice and audio via ElevenLabs and more; new models added as they launch
- Every AI call has a matching /cost endpoint for predictable billing
VEED API
- AI video generation and lip sync endpoints
- Model coverage not documented as a multi-vendor catalog
The details
Rendley Studio vs VEED API, side by side.
| Rendley Studio | VEED API | |
|---|---|---|
| Positioning | Developer-first video platform (SDK + API + MCP) | AI video API derived from a consumer editor |
| In-browser editing SDK | Yes — @rendley/sdk renders client-side (WebCodecs/WebGL) | No confirmed in-browser SDK |
| REST API | Yes — api.rendley.com/v1, OpenAPI, jobs + signed URLs | Yes — generation, lip sync, and editing endpoints |
| Official MCP server | Yes — hosted, 18 tools | No confirmed MCP server |
| Prompt-to-video agent | Yes — /agent/sessions endpoint | AI generation endpoints |
| AI generation models | 25+ aggregated (Veo, Kling, Seedance, Sora, Flux, DALL-E…) | AI generation and lip sync |
| Object storage region | EU — Hetzner, Nuremberg (Germany) | Check vendor docs |
| Pricing model | Plans + credits: Free, $15, $30, $70/mo (1 credit = $0.01) | Not public on the API page — contact/usage-based (verify at source) |
Competitor details are from public pricing and documentation and can change. Verify current specifics on the vendor’s own site.
Credit where due
Where VEED API may fit better
- VEED is a well-known consumer editor with a large feature set, so its API endpoints build on a mature, polished editing product.
- If you want AI-heavy generation and lip sync endpoints without embedding an editor, VEED’s API-only approach can be a quick way to add those features.
- Teams already using VEED’s editor internally may find its API a natural extension of a workflow they know.
- VEED continues to invest in AI video, so its endpoint coverage for generation and lip sync is worth monitoring as it evolves.
Best-in-class AI models, built in
Generate clips, images, and voiceovers without leaving the editor. New models are added as they launch.
KlingVeoSoraSeedanceNano BananaElevenLabs
FAQ
Asked. Answered.
Rendley is developer-first across three surfaces: an in-browser editing SDK, a REST API, and a hosted MCP server, all built on the same engine. VEED’s API exposes AI generation, lip sync, and editing endpoints derived from its consumer editor, with no confirmed in-browser SDK or MCP server.
Create your next video in minutes.
Free to start, with no length caps. Try it on a real project.