Genmo
Genmo is a San Francisco research lab building open-source video generation models. Its flagship release, Mochi 1, is an Apache-2.0 licensed 10B-parameter text-to-video diffusion model (AsymmDiT architecture) with strong prompt adherence and high-fidelity motion. Genmo does NOT publish a first-party hosted developer REST API. Programmatic access to Mochi comes in three honest forms: (1) the open-source model itself, self-hosted via the repo's Python pipeline ("simple composable API"), CLI, Gradio UI, or ComfyUI; (2) third-party hosted inference APIs from partners such as Replicate and fal.ai; and (3) a credit-based consumer web app and Playground at genmo.ai/play. The endpoints documented here for hosted access are modeled from partner documentation and are not operated by Genmo.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Genmo the way a machine reads it — 4 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Genmo scores 19.2/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Genmo
Each block below is one kind of artifact we hold for Genmo. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mochi 1 on Replicate (Third-Party Hosted)
Third-party hosted access to Genmo's Mochi 1 via Replicate's predictions API (model identifier genmoai/mochi-1). Runs on Nvidia H100 hardware, ~$0.42 per run, typically completi...
Mochi v1 on fal.ai (Third-Party Hosted)
Third-party hosted access to Mochi via fal.ai (model identifier fal-ai/mochi-v1), using fal's queue API - submit with prompt, negative_prompt, seed, enable_prompt_expansion, and...
Genmo Mochi Pipeline (Self-Hosted OSS)
The first-party access surface is the open-source model itself. The Mochi repo (Apache-2.0) ships a "simple composable API" in Python - MochiSingleGPUPipeline built from T5Model...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Resources
Every other property we hold for Genmo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/genmo-ai · machine-readable index on apis.io