APIhub Video

View saved version →

---
name: full-edit-video
description: Use when the user wants a finished, edited video from their own footage — "edit this", "make it look great", "a full edit", "add AI shots / b-roll, music and effects", "make mine like this example". Lets the user pick the kind of edit and a look with choose_edit where that tool is available, then runs APIhub's video editor in one job (shots, music, sound effects, headline, captions, zooms and cuts) with full_edit_video after the price is approved.
---

# A full edit of the user's video

Follow the steps in the `video-price-and-status` skill: get the video, the price, the user's yes, `full_edit_video`, `video_status`, the link.

## What it makes

One finished vertical video from the user's footage: pauses and retakes cut, a headline in the first seconds, captions, and — by the kind of edit — shots cut in over the speech (real stock footage or AI-made), music with sound effects, punch-in zooms and flash cuts. Plus a title, a caption and hashtags for posting (nothing is posted).

## Let the user pick: `choose_edit`

When `choose_edit` is among your tools, start there whenever the user brings a video and wants it edited or is not specific about how ("edit this", "make it look good", "make a reel of it"). Call it with the video and nothing else. It only prices: the full edit three ways for this video, with four looks to see; nothing runs and nothing is charged.

- The three kinds: **edit + captions** (the pauses and retakes cut, a headline, captions; the cheapest), **stock footage + music** (that, plus real stock footage of what is said, music and sound effects), **AI shots + effects** (AI-made shots instead of stock, music, sound effects, zooms and flashes; the most expensive).
- The four looks: `clean`, `bold-lime`, `night`, `warm` — the colours and fonts of the captions and the headline, and the mood of the music.
- Where the app shows the card, the user taps a kind, a look and one button. The message that button sends ("Make my video: …, I approve up to N credits") carries `full_edit_video`'s exact arguments, the approval id included: use them as they are for the `full_edit_video` call.
- Where no card is shown (Claude Code, Cursor), tell the user the three kinds with their prices and the four looks in a few short lines (the preview links play), let them pick one of each, and after their OK send that pair's `call` from `choices` as it is. A kind the balance does not cover has no call.
- Do not ask about the style, the music or the shots in text first. A narrow ask goes straight to its own tool: "just captions" → `captions_for_video`, "reels from this podcast" → `reel_from_long_video`.

Without `choose_edit`, price with `get_price` and `task: full_edit_video`, show the price with the short list of what will be in the video, and wait for the yes.

## What to set

- `video`: a link or an upload code (in ChatGPT only, an attached file as `video_file`).
- `tier` and `look`: the kind of edit and the look the user picked in `choose_edit`, or named themselves.
- `example`: when the user picked a card in `show_examples` ("make mine like this"), that card's id — its look becomes this video's.
- `request`: the user's own words about the mood or what to stress, when they gave any.
- `shots`: `ai` (AI-made shots — the most striking, and most of the price), `stock` (real stock footage — much cheaper) or `none`. Offer `stock` when the price matters.
- `music`: `calm`, `warm`, `epic` or `none`.
- `length_seconds`: only when the user wants a set length (15–180). By default the whole clip up to 3 minutes, else about a minute of its strongest part.

Ask nothing more than you need: "make a great edit of this" plus the video is enough. If the finished plan needs more credits than approved, `video_status` says so with the real price: show it and ask again.

View saved version →

---
name: reel-from-long-video
description: Use when the user has a long video (a podcast, a lecture, a webinar, a long talk or interview) and wants short vertical reels, Shorts or TikToks cut from it, with captions and a headline. Runs reel_from_long_video, which finds the strongest self-contained moments by itself or uses the moments the user names.
---

# Reels from a long video

Follow the steps in the `video-price-and-status` skill: get the video, `get_price`, the user's yes, `reel_from_long_video`, `video_status`, the links.

## What to set

- `video`: the link or the upload code. Long files are easier to upload with `start_upload` than to share.
- `count`: how many reels, 1 to 3. Each one comes from a different moment. The price grows with the count, so ask if the user did not say.
- `seconds`: about how long each reel is, 15 to 90. The default is 40.
- `moments`: only when the user names the parts (start and end as seconds or m:ss, for example `"1:35"` to `"2:20"`). Leave it out and APIhub watches the video and picks whole-sentence moments by itself.
- `focus`: optional, one line on what the reels should be about ("the part about pricing").
- `style`: the caption style. `bold` is the default; for a calm talk use `classic`. The `video-captions` skill has the full table.
- `spoken_language`: leave it out to detect it.
- `title`: a short headline in each reel's first 3 seconds, taken from what is said. On by default.

## Handing them over

Each reel is its own video with its own id. Follow each id with `video_status` (it accepts several ids at once) and give the user every link when they are done, with one line on what each reel is about.

View saved version →

---
name: video-captions
description: Use when the user wants captions or subtitles burned into a video (Hebrew, English, Arabic, Russian or another language), wants a talking video turned into a captioned vertical clip, or asks which caption style fits their video. Picks a caption style by the kind of content and runs captions_for_video after the price is approved.
---

# Captions on a video

Follow the steps in the `video-price-and-status` skill: get the video, `get_price`, the user's yes, `captions_for_video`, `video_status`, the link.

## Which style

Pick by what the video is. Name the style you picked in a few words when you show the price, so the user can ask for another. When the user wants to see the styles, call `show_examples` with `kind: caption_styles` — each style plays as a short video with a "Use this style" button.

| The video | Start with | Also fits |
| --- | --- | --- |
| A calm talk, a lecture, a podcast, an interview, an explainer: long speech people read along with | `classic` | `news`, `quiet`, `typewriter`, `underline`, `elegant`, `cinema`, `bubble` |
| An energetic pitch, sales, a hype reel, a hook-driven short: the spoken word marked out | `bold` | `karaoke`, `one-word`, `marker`, `sticker`, `drama`, `scale` |
| Entertainment, humour, a playful or young brand: captions that move | `neon` or `pop` | `bounce`, `handwritten`, `comic`, `shadow`, `lime`, `retro`, `sport` |

If the user names a style, use it. If you can't tell what the video is, use `classic`.

## What to set

- `video`: the link or the upload code — or `video_file` when the user attached the video in the chat.
- `style`: from the table.
- `spoken_language`: leave it out to detect it, or set it when the user says (`he`, `en`, `ar`, `ru`…). Hebrew and Arabic captions are drawn right to left by themselves.
- `captions_language`: only when the user wants the captions in another language than the one spoken (they are translated line by line).
- `shape`: `vertical` (9:16, for Reels, TikTok and Shorts) is the default. Use `original` to keep the video's shape, or `square`, `portrait`, `landscape` when asked.
- `headline`: only when the user wants a short headline in the first 3 seconds (3 to 8 words, in the video's language).
- `cut_pauses`: `true` only when the user wants the silent pauses cut out.

Ask only what you can't infer. "Add Hebrew captions to my video" plus a link is enough to price it.

View saved version →

---
name: video-from-idea
description: Use when the user has only an idea, a topic or a script and no footage, and wants a short narrated video (a faceless reel with a voice-over, stock footage and captions). Writes the script with the user first, then runs video_from_idea after the words and the price are approved.
---

# A video from an idea

Follow the steps in the `video-price-and-status` skill for the price, the yes, `video_from_idea`, `video_status` and the link. There is no video to get: you write the words first.

## 1. Write the script with the user

- Write the exact words the voice will say: about 60 to 150 words for a 30 to 60 second video, in the language the video should be in.
- Open with a line that makes people stop scrolling, keep sentences short, end with one clear point.
- Show the script and ask for changes. Use only the version the user approved.

## 2. What to set

- `script`: the approved words.
- `voice`: `woman` (the default) or `man`.
- `language`: the script's language (`he`, `en`, `ru`…), or leave it out to detect it.
- `topic`: one line on what the video is about. It guides the choice of stock footage.
- `mood`: how the voice should sound, for example "warm and calm" or "energetic".
- `style`: the caption style; `bold` is the default. The `video-captions` skill has the full table.

## 3. Price, yes, run

Price it with `get_price`, show the price, wait for the yes, run it once, follow it to the end and give the link. If the user changes the script after the yes, price it again.

View saved version →

---
name: video-price-and-status
description: Use when the user asks APIhub to make or edit a video, asks what a video job costs, how many credits they have, or whether their video is ready. Covers getting the video (a link, start_upload, or a file attached where the app hands it over), pricing with get_price, waiting for the user's explicit OK, running the task once, following it with video_status and handing over the finished link.
---

# The steps of every APIhub video job

Every job follows the same six steps. The task skills (captions, reels, video from an idea, full edit) only add what to ask for.

## 1. Get the video

- **A public link works:** a direct link to the file (`https://…/clip.mp4`), or a Google Drive or Dropbox link shared with "anyone with the link".
- **A file on the user's phone or computer:** call `start_upload`. It shows an upload card with one button; when the file arrives the card says so and the chat continues by itself (or the user says "done" — then check `upload_status`). Pass the upload code as the video.
- **Attached in this chat:** only in ChatGPT, which hands the file to the tool — pass it as `video_file`, no link and no upload page needed. In Claude, Cursor and the other apps an attached file does not reach APIhub: ask for a link, or call `start_upload`.
- **A YouTube, Instagram or TikTok page is not a file.** Ask for the file itself, or for an upload.

## 2. Price it

Call `get_price` with the task name (`captions_for_video`, `reel_from_long_video`, `video_from_idea` or `full_edit_video`) and exactly the arguments you will run with. Nothing runs and nothing is charged. Its answer has a ready `call`: after the yes, send exactly that.

The one exception: a video the user wants edited without saying how. When `choose_edit` is among your tools, start there (the `full-edit-video` skill): it prices three kinds of edit for that video and shows four looks, nothing is charged, and each choice carries its own `call` and approval.

## 3. Show the price and wait for a yes

- Tell the user the price in credits and their balance, in their language, in one or two short lines.
- Wait for an explicit yes. Silence, "maybe" or "sounds interesting" is not a yes.
- A budget the user named earlier ("up to 50 credits") covers only a price within it. Above it, show the real price and ask.
- If the balance does not cover the price, say so plainly — the balance, the price — and stop. Nothing is charged. Pass on the link the answer gives (where the user can read how credits work); do not offer to add credits in the chat.

## 4. Run it once

Call the task tool with the same arguments, plus:

- `approved_estimate_id`: the id that `get_price` returned;
- `approved_credits`: the number the user agreed to, never one you chose for them.

If anything changes after the yes (style, length, language, the video), price it again and ask again.

## 5. Follow it to the end

A job answers with an id and the status `processing`. Call `video_status` with that id about every 15 seconds until it is `completed` or `failed`. Never start the same job again while it runs. Captions on a clip of about 40 seconds are usually ready in about a minute; reels and a full edit take a few minutes.

## 6. Hand it over

Give the link to the finished video and say what it cost. The video is also in the user's APIhub account. If the job failed, say so in plain words; failed work is not charged.

## Credits and wording

- `get_balance` shows the balance. Talk about prices and balances in credits only.
- When the user is unsure what to make, or asks for examples or caption styles, call `show_examples` (it shows them as running videos) — never list styles as text.
- Keep it short and plain: the user may never have edited a video. No technical words such as API, render or endpoint.