# x402 Multi Hub - YouTube to Telegram

> x402 Multi Hub - YouTube to Telegram is a paid API for AI agents from x402-multi-hub.vercel.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-12).

Downloads a YouTube video/audio and sends it to Telegram via the x402 paid API gateway

## Facts

- Endpoint: POST https://x402-multi-hub.vercel.app/api/youtube-to-telegram?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-multi-hub-youtube-to-telegram-3a7946e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__K1CmhaWjKU-jpvJKSX8D

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 x402-multi-hub-youtube-to-telegram-3a7946e4 -d '<json body>'
```

Example prompt: Download the YouTube video with ID dQw4w9WgXcQ as an mp4 at 720p quality and send it to Telegram, notifying me via my webhook at https://myserver.com/hook when it's done.

## When to prefer this

Use this endpoint when you need to programmatically download a YouTube video or audio track and automatically deliver it to Telegram in a single API call, especially when automating media pipelines with async webhook callbacks.

## Known failure modes

- Invalid or unavailable YouTube video ID returns an error or empty data
- Unsupported quality or format combination may cause download failure
- Webhook URL unreachable results in missed async notification
- Payment failure via x402 protocol blocks the request before processing
- Large video files may time out or be rejected by Telegram file size limits

## How this service works

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

## Output

Returns a data object confirming the download and Telegram delivery status; if a webhook_url was provided, an async callback is sent when the media transfer completes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "video_id"
 ],
 "properties": {
  "quality": {
   "type": "string",
   "description": "best, worst, 1080p, 720p, 480p, 360p"
  },
  "video_id": {
   "type": "string",
   "description": "YouTube video ID"
  },
  "file_format": {
   "type": "string",
   "description": "m4a, mp3, mp4"
  },
  "webhook_url": {
   "type": "string",
   "description": "Webhook URL for async notification"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-multi-hub-youtube-to-telegram-3a7946e4/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)