Authentication

Sourced from the LiquidClips dataset · 4,700,802 creatorsBy Daniel Diyepriye, Founder, LiquidClipsUpdated Jul 2026· 3 min read

The public resolve endpoint is open so you can build against real data today. Keys arrive with the versioned platform API, which unlocks higher limits, cross-creator clip search, and CPM lookup.

01Auth today

The resolve endpoint requires no authentication. Call it and you get real channel data back. It is rate limited per IP to keep it honest, so batch responsibly.

no key required

# the public resolve endpoint needs no key today
curl "https://liquidclips.app/api/resolve?url=@mkbhd"

02API keys (coming)

The versioned API at api.liquidclips.app/v1 will use bearer keys (lc_live_... and lc_test_...) sent in the Authorization header. This is the shape it will take:

coming soon

# how keyed requests will work on the versioned API
curl "https://api.liquidclips.app/v1/creators/@mkbhd" \
  -H "Authorization: Bearer lc_live_your_key_here"

◱ Not live yet

The versioned API and keys are on the build path, not live. The endpoint above is illustrative. Join the waitlist to get a key the day it ships.

◱ Coming soon

Get on the the platform API waitlist

This is on the build path, not live yet. Drop your email and Kade tells you the day it ships. No spam, one message.

03Rate limits

The public resolve endpoint is capped per IP and caches resolved channels for six hours, so repeat lookups of the same channel are free. Keyed tiers on the versioned API will raise those limits and add usage reporting.