# YouTube Live HLS Stream Fetcher

> YouTube Live HLS Stream Fetcher is a paid API for AI agents from x402-multi-hub.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-11).

Retrieves HLS stream data for a YouTube live video given its video ID

## Facts

- Endpoint: POST https://x402-multi-hub.vercel.app/api/youtube-live-hls?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/youtube-live-hls-stream-fetcher-ec9ae4cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ej3FMfOSJ2ZyzfziOfpKK

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability youtube-live-hls-stream-fetcher-ec9ae4cf -d '<json body>'
```

Example prompt: Can you get the HLS live stream data for the YouTube video with ID 'dQw4w9WgXcQ'? I need the stream details to play it.

## When to prefer this

Use this endpoint when you need to programmatically retrieve HLS stream data for a YouTube live broadcast by video ID, especially in automated workflows that accept micropayments via the x402 protocol. Prefer this when integrating live stream playback into apps or pipelines without direct YouTube API credentials.

## Known failure modes

- Invalid or non-existent video ID returns error or empty data
- Video is not a live stream (is a regular video) may return empty or error response
- Video is private or region-restricted may fail to return stream data
- Payment failure via x402 protocol blocks access to the endpoint
- Rate limiting or quota exceeded returns error

## How this service works

16 paid endpoints: Jobs, Business, Telegram, YouTube, Shopee. Powered by x402 protocol.

## Output

Returns an object containing HLS stream data for the specified YouTube live video, including stream URLs and associated metadata needed for playback.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "video_id"
 ],
 "properties": {
  "video_id": {
   "type": "string",
   "description": "YouTube live video ID"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/youtube-live-hls-stream-fetcher-ec9ae4cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-multi-hub.vercel.app](https://www.zero.xyz/host/x402-multi-hub.vercel.app/llms.txt)