ForHosting KIT · SEO

YouTube description

A video with no chapters and a three-line description is invisible to both viewers and search. This endpoint takes a video's content and returns a title option, a full description, a tag list and timestamped chapters — the metadata that decides whether a video gets found at all.

● BetaPer request + per video$0.003

Run — $0.003 + $0.0135/video How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

Why metadata carries so much weight on video

Unlike a web page, a video can't be skimmed by a search algorithm the way text can — the title, description and tags do most of the work of telling both viewers and search what's actually inside. A creator who nails the footage but writes a rushed two-sentence description is leaving the discovery half of the job undone, and that gap is exactly what this endpoint closes.

What comes back and why chapters matter

The response includes a title suggestion, a description structured for both readability and search, a relevant tag list, and timestamped chapters marking the video's key moments. Chapters do double duty: they let viewers jump straight to the part they want, and they give the platform explicit structure to understand a long video as a sequence of distinct topics rather than one undifferentiated block.

How video description writing has changed

Early video platforms treated the description as an afterthought — a caption box under the real content. That changed once creators noticed that a well-built description with timestamps, links and a clear summary measurably affected how videos got recommended, and description-writing became its own skill, distinct from scripting or editing. This endpoint packages that skill into a request instead of a manual, video-by-video exercise.

Who saves the most time here

Channels publishing on any kind of regular schedule feel this most — writing a genuinely good description for every upload is the task that gets rushed or skipped when the backlog builds up. Educational and long-form channels benefit especially from the chapter generation, since a 40-minute video without chapters loses viewers who can't find the section they came for.

What you still control

The output is a strong draft, not a final publish — titles should still match your channel's voice, and any chapters or tags referencing sensitive claims deserve a human check before going live. Results are delivered by signed webhook or a 24-hour signed link, and submitted video content is deleted after the retention window and never used for training.

What you can do with it

Weekly upload schedule

A creator publishing every Thursday generates title, description and chapters as soon as editing wraps, instead of writing metadata under deadline pressure.

Long-form educational videos

A course channel gets timestamped chapters for a 90-minute lecture automatically, letting students jump straight to the topic they need.

Back-catalog cleanup

A channel with two years of videos and thin descriptions batches its older uploads through the endpoint to add proper chapters and tags retroactively.

Multi-channel content teams

An agency managing several client channels standardizes description quality across all of them without hiring a dedicated metadata writer.

FAQ

What does the YouTube description generator API return?

A title suggestion, a full description, a relevant tag list and timestamped chapters for the video you submit.

Do I need to submit the video file itself?

You submit the video's content details for processing; check the endpoint's accepted input formats before integrating.

Is there a free trial?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

How is it priced?

$0.003 per request plus $0.0135 per video processed.

Can I process many videos in one batch?

Yes, requests are asynchronous, so you can queue an entire backlog and collect each video's metadata as it completes.

Does it generate chapters automatically?

Yes, timestamped chapters marking key moments in the video are included in the response alongside the title, description and tags.

How do I receive the results?

By signed webhook, recommended for automated pipelines, or a signed link valid for 24 hours.

What happens if a request fails?

It's retried automatically up to three times and is never charged if it ultimately fails; you get a clear error instead.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/seo/youtube-meta

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/seo/youtube-meta \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/seo/youtube-meta", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/seo/youtube-meta",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/seo/youtube-meta", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/seo/youtube-meta", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "seo.youtube_meta",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per video$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →