How to get an AI summary of a Utilities file video
POST request to /v1/video/summarize with your input. You get clean JSON back in seconds for 1 credit/min +1 per call — no OAuth, scraping or platform SDKs. Whisper + AI summary of an uploaded file — transcript included; 1 credit/min + 1.How to get an AI summary of a Utilities file video (step by step)
- 1
Get a free API key
Create a free Captapi account (100 credits, no card) and generate an API key from the dashboard.
- 2
Call the Video File Summarizer API
Send an authenticated POST request to /v1/video/summarize with your input. No OAuth, no scraping setup.
- 3
Read the JSON response
Parse the clean JSON response. Pass cache=true for a free 24h cache hit; default is always fresh.
Code example
curl -X POST "https://api.captapi.com/v1/video/summarize" \
-H "Authorization: Bearer capt_live_..." \
-F "file=@video.mp4"
# or: -H "x-api-key: capt_live_..."What the response looks like
{
"success": true,
"data": {
"filename": "sample.mp4",
"summary": "This walkthrough shows how teams extract structured data from social video at scale without standing up scrapers or OAuth apps. It covers a single API key across platforms, shared caching, and why clean JSON beats brittle HTML parses.\n\nThe speaker contrasts fresh fetches with cache hits: the same profile call can drop from multi-second billed work to a sub-second free response. They also stress verifying per-minute Whisper billing via durationSeconds and creditsCharged in the response.\n\nClosing takeaways focus on bringing your own media files for transcript-plus-summary in one POST, and using request logs to prove cache savings.",
"keyPoints": [
"One Captapi key works across supported platforms — no per-network OAuth.",
"Pass cache=true for a free 24h shared cache hit on social endpoints.",
"Whisper file endpoints bill per minute; read durationSeconds and creditsCharged.",
"Summarize returns the full transcript alongside summary/keyPoints/topics.",
"Short clips yield shorter summaries; longer audio aims for 2–3 paragraphs and 4–8 bullets.",
"Account request history exposes cacheHit and responseTimeMs side by side.",
"Use multipart POST (-F file=@path) — never put the file in the query string.",
"Empty/no-speech audio returns HTTP 422 on summarize (cannot summarize silence)."
],
"topics": [
"APIs",
"data extraction",
"automation",
"billing",
"caching"
],
"sentiment": "positive",
"transcript": "Hey everyone, welcome back to the channel. Today we are breaking down structured data APIs for social video. First, one API key across platforms beats stitching OAuth apps together. Second, the shared cache turns expensive profile lookups into free sub-second hits. Third, when you upload a file for Whisper, always check durationSeconds against creditsCharged. Finally, summarize gives you the AI digest plus the full transcript in the same JSON payload.",
"transcriptSegments": [
{
"text": "Hey everyone, welcome back to the channel. Today we are breaking down structured data APIs for social video.",
"start": 0,
"duration": 8.2,
"end": 8.2,
"timestamp": "00:00"
},
{
"text": "First, one API key across platforms beats stitching OAuth apps together.",
"start": 8.2,
"duration": 5.1,
"end": 13.3,
"timestamp": "00:08"
},
{
"text": "Second, the shared cache turns expensive profile lookups into free sub-second hits.",
"start": 13.3,
"duration": 5.4,
"end": 18.7,
"timestamp": "00:13"
},
{
"text": "Third, when you upload a file for Whisper, always check durationSeconds against creditsCharged.",
"start": 18.7,
"duration": 6,
"end": 24.7,
"timestamp": "00:18"
},
{
"text": "Finally, summarize gives you the AI digest plus the full transcript in the same JSON payload.",
"start": 24.7,
"duration": 5.5,
"end": 30.2,
"timestamp": "00:24"
}
],
"wordCount": 70,
"segments": 5,
"language": "english",
"durationSeconds": 30.2,
"duration": 30.2,
"creditsCharged": 2,
"noSpeech": false
}
}Billing metadata (credits charged, cache hit/miss) is returned in the X-Captapi-Credits and X-Captapi-Cache response headers.
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
| file | file | Yes | Video or audio file (multipart form field — use -F file=@path, not a query string). Max 200MB / 60 minutes. |
| language | string | No | ISO-639-1 Whisper language hint, e.g. "en" or "tr". Omit to auto-detect. |
| translate | boolean | No | When true, translate speech to English before summarizing. Default false. |
| timestampGranularity | string | No | segment (default) or word. |
Frequently asked questions
What does the Video File Summarizer API do?
The Video File Summarizer API lets you generate an AI summary with key points and topics from a public Utilities uploaded video or audio file using one POST request to /v1/video/summarize. It returns clean JSON — no OAuth or infrastructure setup required.
How many credits does the Video File Summarizer API cost?
Billing is 1 credit per minute of audio (rounded up) plus 1 credit for the AI summary. The response includes durationSeconds and creditsCharged so you can verify the line item. No-speech uploads return HTTP 422 and are not charged for the summary step.
Do I need a Utilities API key or OAuth?
No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.
Which AI model powers the summaries?
Summaries are generated with GPT-4o-mini for a strong balance of quality, speed, and cost, built on top of the transcript.
Is the Video File Summarizer API suitable for production use?
Yes. It is a stable REST endpoint with predictable JSON. Upload via multipart form field file (POST) — see the cURL sample. Use durationSeconds / creditsCharged to verify per-minute billing.
Ready to get an AI summary of a Utilities file video?
Start free with 100 credits — no credit card required.
Get your free API key