TwelveLabs API Review 2026: Pegasus & Marengo
TwelveLabs (twelvelabs.io) is a San Francisco-based AI startup that builds a dedicated video-understanding API. The company raised a $100M Series B in 2026 and is one of the top-funded pure-play video-AI companies in the world. Its flagship product is the Pegasus model family (Pegasus 1.5 in production, Pegasus 1.2 as a lower-cost previous-generation option) and the Marengo video foundation model (Marengo 3.0, 27B parameters), which together cover the full stack from "what is in this video" to "find the moment the speaker mentions X." For an engineer evaluating a video understanding API in August 2026, TwelveLabs matters because it is the only first-party provider that fuses visual frames, temporal sequence, speech audio, and on-screen text into a single natural-language description — and it ships a free 600-minute tier that is enough to PoC a mid-size project without a credit card. Read the full TwelveLabs provider page for the structured comparison table.
What is TwelveLabs, and why does its API matter in 2026?
TwelveLabs is the AI arm of a 2021-founded San Francisco startup focused exclusively on video understanding — not generation. Through its REST API at api.twelvelabs.io/v1.3, developers can submit videos, get them indexed, then run four core operations against the index:
- Search — natural-language or example-based retrieval across an index (find clips matching "the moment the speaker mentions pricing");
- Embed — generate Marengo multimodal embeddings for downstream RAG pipelines;
- Analyze — run Pegasus to classify, segment, or extract structured information from a video;
- Gist — generate a Pegasus natural-language summary of a video.
Its positioning in the 2026 video AI market:
- Multimodal fusion is the headline. Pegasus 1.5 jointly encodes visual frames + temporal sequence + speech audio + on-screen text in a single transformer pass. Competing models often stitch modalities post-hoc, which loses causal relationships between speech and visual change.
- Marengo is the foundation. Marengo 3.0 is a 27B-parameter video foundation model producing embeddings that span all four modalities, enabling any-to-any retrieval: text-to-video, video-to-video, image-to-video, audio-to-video.
- Developer surface is mature. Official SDKs for Python / Node / Go / Java, OpenAPI 3 spec, an MCP server for AI agents (Claude Code, Cursor), Playground, and a $100M Series B funding round that puts the company on solid enterprise footing.
This review covers the TwelveLabs API from the perspective of an engineer integrating it in August 2026: the Pegasus 1.5 / 1.2 model lineup, the Marengo 3.0 embedding model, the per-minute pricing system, the indexing and Search / Embed / Analyze workflows, and how TwelveLabs compares to OpenAI GPT-4o, Google Gemini 2.5 Pro video, and the generation APIs (Kling, Luma, Runway) for video AI tasks. If you need a side-by-side view, the visual understanding comparison lists how TwelveLabs stacks up against GPT-4o, Gemini, and Claude for image + video tasks.
The TwelveLabs model lineup in 2026
TwelveLabs currently ships three production models across two layers:
| Model | Layer | Output | Best for |
|---|---|---|---|
| Pegasus 1.5 | Generative / analytic (flagship) | Natural-language gist, classification, structured extraction | Production video understanding where multimodal fusion matters |
| Pegasus 1.2 | Generative / analytic (previous gen) | Same as 1.5, lower-fidelity fusion | Cost-sensitive workloads; same API surface, lower cost-per-minute |
| Marengo 3.0 | Embedding foundation (27B params) | Multimodal embeddings (frame / audio / speech / text) | RAG, any-to-any retrieval, cross-video search |
Pegasus 1.5 and Pegasus 1.2 share the same API surface and per-minute billing structure — the difference is the quality of the multimodal fusion. Marengo 3.0 is a separate model used for retrieval; you call it via POST /embed on an indexed video and get back an embedding vector that can be stored in any vector database (Pinecone, Weaviate, Qdrant, Chroma, or even an in-memory numpy array).
TwelveLabs pricing: per-minute video, per-token text
TwelveLabs is unusual among video AI APIs in that it bills per minute of input video, not per token. This is closer to how humans think about video cost (a 10-minute clip costs 10x a 1-minute clip) and easier to forecast than a token-metered model. Pricing verified 2026-08-18 from the official twelvelabs.io/pricing page:
| Component | Price | Billed | Notes |
|---|---|---|---|
| Video indexing | $0.042/min | One-time at index time | Pegasus 1.2 / 1.5 — both models share the same indexing cost |
| Input video | $0.021/min | Per API call | Search, Analyze, Segment, RAG calls |
| Output text | $0.0075/1k tokens | Per call | Pegasus natural-language generation |
| Marengo embedding infrastructure | $0.0015/indexed minute/month | Monthly recurring | Storage cost for the index — separate from indexing one-time fee |
| Free signup credit | 600 minutes | Cumulative | Enough to PoC a mid-size project; no credit card required |
| Developer plan subscription | $0/month | — | Pay-as-you-go beyond the free tier; no monthly minimum |
For a concrete cost example: a 100-hour video archive indexed once ($0.042 × 6,000 = $252) and queried 1,000 times for 5-second clips ($0.021 × ~83 hours of input = $1.74) plus $0.0075 per 1k tokens for any text output. Storage at $0.0015/indexed minute/month = $9/month. So a 100-hour archive that gets 1,000 searches a month costs roughly $263 upfront + $10/month recurring. Compared to building the same pipeline with GPT-4o video input (which charges per token on input frames and per call), TwelveLabs is usually cheaper for long-form video where you repeatedly query the same archive.
How the TwelveLabs API actually works
The TwelveLabs API uses an asynchronous indexing task model: submit a video (or reference an existing asset) → poll for the index to be ready → call Search / Embed / Analyze against the index. The MCP server at https://docs.twelvelabs.io/_mcp/server lets Claude Code and Cursor call Search / Analyze / Embed directly without writing integration code.
Step 1: Index a video. POST a video file or a URL to /v1.3/tasks. The API returns a task ID; poll GET /v1.3/tasks/{task_id} until status is ready. Typical indexing latency is 30 seconds for a 5-minute clip, several minutes for an hour-long video.
Step 2: Search the index. Once indexed, POST a text or image query to /v1.3/search. The API returns ranked matching clips with timestamps. For example, querying an indexed product demo for "the moment the speaker mentions pricing" returns the precise 12-second clip where pricing is discussed, even if nothing visual signals the topic.
Step 3: Generate embeddings. Call POST /v1.3/embed on an indexed video to get back Marengo 3.0 multimodal embeddings. Store these in your vector database of choice; combine with text embeddings for hybrid retrieval.
Step 4: Run analysis. Call POST /v1.3/analyze for structured extraction (classification, named entities, sentiment by timestamp) or POST /v1.3/gist for a Pegasus-generated natural-language summary.
The official Python SDK (twelvelabs on PyPI) wraps all four steps in a single client class with helper methods for the common patterns. Example: client.task.index(video_file="demo.mp4") starts the index, client.search.query(index_id=..., query="the moment the speaker mentions pricing") returns ranked clips.
TwelveLabs vs OpenAI vs Google Gemini vs video generation APIs
TwelveLabs occupies a specific niche — video understanding — that overlaps with general multimodal LLMs (OpenAI GPT-4o, Google Gemini 2.5 Pro) and complements video generation APIs (Kling, Luma, Runway, Veo). Here is how the categories break down:
| Capability | TwelveLabs | OpenAI GPT-4o | Gemini 2.5 Pro | Kling / Luma / Runway |
|---|---|---|---|---|
| Generate video | No | No | No | Yes (primary) |
| Understand hour-long video | Yes (specialty) | Limited (frame sampling) | Yes (up to 2h) | N/A |
| Temporal-precise clip retrieval | Yes (core) | Approximate | Yes | N/A |
| Multimodal embeddings (frame+audio+speech+text) | Yes (Marengo 3.0) | No (text + image only) | Partial | No |
| Speech-aware search | Yes (native) | Requires separate ASR | Yes (native) | N/A |
| Free tier | 600 minutes | Limited API credits | Free tier with limits | Limited free credits |
| China access | Proxy required | Proxy required | Proxy / Vertex AI | Kling is China-direct |
The right combination for a production video AI stack in 2026 is usually TwelveLabs for understanding + a generation API (Kling, Luma, Runway) for creation. The two halves complement each other: generation APIs make new video from text or images; TwelveLabs makes existing video searchable, structured, and retrievable. TwelveLabs sits cleanly alongside OpenAI or Anthropic as a specialist preprocessor — call TwelveLabs first to find the relevant clip or extract a gist, then feed that text to a general LLM for downstream reasoning. For the full pricing table and SDK install instructions, see the official TwelveLabs API reference.
Limitations to know
- Per-minute billing requires video-aware cost models. A 1,000-hour surveillance archive is not economically comparable to a 1,000-hour text corpus; TwelveLabs bills per minute, so the math needs to be redone.
- Indexing is async. Typical 30 seconds for a 5-minute clip, several minutes for an hour-long video. Not suitable for real-time generation use cases (use Kling / Luma for those).
- No mainland China endpoint. Production deployment from China requires a proxy or Enterprise private deployment.
- Pegasus 1.5 vs 1.2 marginal gain. On pure-text or pure-frame tasks, the gain over Pegasus 1.2 is small; the 1.5 advantage is in joint multimodal scenarios.
- Knowledge Store / Agents still in research preview. The cross-video Q&A API surface may change before general availability.
- No function calling or tool use. TwelveLabs is a specialist understanding API, not an LLM. Pair with GPT-4o, Claude, or a local LLM for downstream reasoning.
- No affiliate program. Unlike Cloudflare, OpenRouter, or some others, there is no partner revenue share.
Verdict
TwelveLabs is the right choice when video understanding is the primary task — lecture search, surveillance archive retrieval, ad library Q&A, sports footage indexing, training video navigation. The 600-minute free tier is generous enough to validate a use case before paying. For multimodal RAG where video is one of several sources, TwelveLabs + a general LLM is the standard 2026 pattern. For pure video generation, use Kling, Luma, or Runway instead. For pure text LLMs, TwelveLabs is irrelevant.
Where it wins: temporally-precise clip retrieval on long-form video, joint frame+audio+speech+text fusion, free 600 minutes for PoC work, mature SDKs and MCP server for AI agents.
Where it loses: no mainland China endpoint, no real-time response, per-minute billing requires new cost models, no function calling for downstream tool use.
Sources verified 2026-08-18: TwelveLabs pricing and model lineup from the official twelvelabs.io/pricing page (Pegasus 1.2 / 1.5, Marengo 3.0); API surface and endpoint list from docs.twelvelabs.io/api-reference (v1.3 REST API); Free plan 600-minute detail from twelvelabs.io/pricing FAQ; Series B funding announcement on twelvelabs.io homepage. No affiliate relationship with TwelveLabs.