Supported Today
- API-key protected status checks
- Public YouTube ID and URL normalization
- Authenticated resolve requests
- Verified stream variant metadata
Phase 4B frontend
A server-rendered control surface for a public YouTube media API with strict API keys, bounded provider work, safe temporary URL validation, and clear usage feedback.
Keys use server-side hashes and lifecycle state. Browser tools never put keys in query strings, cookies, or server-rendered HTML.
Cached responses target sub-300 ms. Fresh resolution targets 1-2 seconds where upstream behavior permits. These are goals, not guarantees.
Use either X-API-Key or Authorization: Bearer. If both are present and differ, the request is rejected.
curl -X POST "http://127.0.0.1:18000/api/v1/youtube/resolve" \
-H "X-API-Key: eyt_live_example_REPLACE_ME" \
-H "Content-Type: application/json" \
-d '{"input":"https://youtu.be/dQw4w9WgXcQ","media_type":"video"}'
Safe process and dependency readiness only. No hosts, credentials, or topology are exposed.