Faucet API
One endpoint for resolving, rewriting, and proxying streams. Register a domain, grab a key, and ship.
How it works
Faucet sits between your app and the places the video actually comes from, handling resolution, validation, and playback delivery so your code only ever deals with one shape of response: ask for a title, get back a stream URL you can play.
Create an account, generate a key, and register the domains allowed to use it — all from your API dashboard. Then call the endpoint with a content ID and type. That single request returns a proxied HLS URL, plus whatever metadata you need to build a player: which source answered, the stream format, and any captions or alternate servers available to you.
Availability depends on your plan. Faucet One (free) is served by a single source, while Faucet Plus falls back across every available source, so when one is having a bad day your users usually never notice. Because the response always looks the same, your app never has to know which backend actually served the stream.
Heads up: the source used by the free tier is currently degraded and intermittently failing to return streams. See Current Issues in the docs for details and workarounds.
Limits
| Feature | Faucet One | Faucet Plus |
|---|---|---|
| Sources | Source 1 | All (current + future) |
| Rate limit | 10 req / s | 40 req / s |
| API keys | 1 | 3 |
| Authorized domains | 1 | Unlimited |
| Multi-source fallback | — | Automatic |
| New source access | — | Early |
| Support | Discord | Priority |
Pricing
A note on source
The resolution layer — how Faucet finds, validates, and falls back between sources — is the actual product. It's the part that took the most time, gets touched the most, and is the reason the API stays up when individual sources don't.
Opening it up would hand that work to anyone running a clone, and the abuse that follows would fall back on us to clean up. Closed source keeps the service reliable for the people actually paying for it and lets us ship fixes without coordinating a fork.
The API is fully documented, the client side is yours to build however you want, and we're responsive on Discord. That's the trade.