Getting started
The LiquidClips API turns a YouTube link into the thing that matters: the clippable moments inside it, the real numbers behind them, and what a clip is worth. One call, real data, no key required to start.
01What the API does
Paste a channel URL, an @handle, or a channel name and the resolver reads that channel straight from the YouTube Data API. You get the live subscriber count, total views, video count, a sample of recent uploads with their durations and views, and a conservative estimate of how many clips sit inside the catalogue. It is the same engine behind every creator page on this site.
Every number the API returns is pulled live from YouTube. A channel that cannot be resolved returns ok: false with a reason, never a fabricated channel. The clip estimate is labelled and conservative, not a promise.
02Base URL
The versioned platform API (cross-creator clip search, CPM lookup, campaign data) will live at https://api.liquidclips.app/v1. See authentication for the key model that ships with it.
03Your first call
Resolve a channel. The only required parameter is url, which accepts a full YouTube URL, an @handle, a UC... channel id, or a plain channel name.
curl "https://liquidclips.app/api/resolve?url=@mkbhd"04The response
A resolved channel returns its identity, live stats, a recent-uploads sample, and the conservative clip estimate.
{
"ok": true,
"channel": "Marques Brownlee",
"handle": "@mkbhd",
"channelId": "UCBJycsmduvYEL83R_U4JriQ",
"subs": 20100000,
"totalViews": 4200000000,
"videoCount": 1800,
"estClips": 42,
"estClipsBasis": "recent long-form uploads x6 clips (conservative floor)",
"videos": [ { "videoId": "...", "title": "...", "views": 3400000, "durationSec": 1120 } ]
}| Field | Type | What it is |
|---|---|---|
| channel | string | The channel title, live from YouTube. |
| subs | number | Subscriber count at request time. |
| videos | array | Recent uploads with title, views, and durationSec. |
| estClips | number | Conservative clip estimate. See estClipsBasis for the model. |
05What is coming
The resolve endpoint is live today. Next on the path: API keys, a versioned REST surface, cross-creator clip search, a CPM lookup endpoint, the Kade MCP server, and official SDKs and a CLI. Each ships with a waitlist so you hear the day it lands.
