Usage-priced · no per-seat
Per-conversion pricing, not per-seat. Build it into a SaaS, build it into an internal tool, build it into a script — same price.
The conversion engines that power morph.cool are wrapped behind a REST API. POST a file, GET the converted result. No queue, no callback URL.
Image, audio, video, PDF, document, archive — every conversion path Morph ships on the consumer side is exposed as an endpoint.
Per-conversion pricing, not per-seat. Build it into a SaaS, build it into an internal tool, build it into a script — same price.
Synchronous for small files, webhook callback for big jobs. Idempotency keys for safe retries. Standard auth via bearer token.
The Artboard image stack, the Flowcut transcription pipeline, the Soundbend mastering chain — same code paths the consumer app uses. No second-tier port.
Verbs, not toolkits. artboard.gen_image, flashcut.transcribe, soundbend.master. Compose them in agent loops without the orchestration tax.
The endpoints we ship are the endpoints we ship. MorphVision stays internal — that's a moat decision, not a roadmap promise.
Our video-intelligence engine ships in the consumer app and powers internal tooling. It is never licensed, never in the API tier, and not negotiable. Other engines (Artboard, Flowcut, Soundbend, PDF, OCR, MorphAudioIntel) are on the roadmap to license. MorphVision protects the moat.
Typed clients for Node, Python, and Go. One install, every endpoint, streaming responses where it matters.
CLI · RoadmapPipe-friendly CLI for scripting batch jobs. morph artboard gen, morph flashcut transcribe, in/out via stdin and stdout.
The consumer Morph runs entirely in the browser — no upload, no server. The API runs the same engines on a tightly-scoped server tier so AI agents and pipelines that can't live in a browser can still use the work. Same engines, different host. The architectures don't compete; they cover different jobs.
The API tier is priced separately because there is an infrastructure cost per call. Keeping these economically distinct is what protects the consumer commitment.
If you're building an agent that needs to generate, edit, transcribe, master, or convert media at machine speed — and you'd rather not stitch eight vendors together with auth and retries — talk to us. [email protected]