Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GetYouTubeTranscript API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetyoutubetranscript.com%2Fgetyoutubetranscript" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetyoutubetranscript.com%2Fgetyoutubetranscript" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with GetYouTubeTranscript API.
Retrieve the full transcript of a YouTube video by URL or video ID
List the caption languages available for a given video
Search YouTube for matching videos or channels
Resolve a channel handle or URL to its channel ID
List every video in a playlist or uploaded by a channel
GET STARTED
Queue transcripts for up to 100 videos in a single batch request
Check the remaining credit balance for the active key
Patterns agents use GetYouTubeTranscript API for, with concrete tasks.
★ Agent-driven video research
An AI agent researching a topic searches YouTube for relevant videos, resolves the best channel, and pulls each video's transcript so it can summarise or quote the spoken content. The GetYouTubeTranscript API returns transcripts plus the search and channel metadata needed to pick sources, and through Jentic the agent discovers and calls these operations by intent without hand-wiring the key.
Search YouTube for the three most relevant videos on a topic, fetch each transcript, and return a sourced summary
Bulk transcript extraction
Content teams that need transcripts for a large archive list a channel's uploads or a playlist and queue every video for transcript extraction in batches of up to 100. The batch endpoint returns a job that can be polled for status and paged results, so a pipeline can process a whole channel without issuing one request per video.
List every video in a playlist and queue all of them for transcript extraction in a single batch, then poll until the job completes
Caption language discovery
Before requesting a transcript an agent checks which caption languages a video provides, then fetches the transcript in the language the user asked for. This avoids wasted calls on videos with no captions and lets a localisation workflow pick the correct source language for translation.
List the caption languages for a video and fetch the transcript in English if it is available
13 endpoints — the getyoutubetranscript api returns the caption transcript of any youtube video and exposes the surrounding metadata an agent needs to find the right video first.
METHOD
PATH
DESCRIPTION
/transcript
Get a YouTube video transcript
/transcript/languages
List a video's caption languages
/search
Search YouTube videos or channels
/playlist
List every video in a playlist
/channel/videos
List every video a channel has uploaded
/batch
Queue transcripts for up to 100 videos
/transcript
Get a YouTube video transcript
/transcript/languages
List a video's caption languages
/search
Search YouTube videos or channels
/playlist
List every video in a playlist
/channel/videos
List every video a channel has uploaded
/batch
Queue transcripts for up to 100 videos
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GetYouTubeTranscript API by hand means minting a key through its signup flow, choosing whether to send it as a bearer token or in the x-api-key header, and tracking credit spend yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which operations the agent may call, so a key that can read transcripts and search does not also have to expose the signup or batch-queueing operations unless you add them. GetYouTubeTranscript carries the video, channel, and playlist targets as query parameters rather than URL path ids, so rules bound which operations your agent runs.
Credential isolation
Your GetYouTubeTranscript key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a YouTube video transcript' or 'search YouTube videos', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GetYouTubeTranscript API through Jentic.
What authentication does the GetYouTubeTranscript API use?
The GetYouTubeTranscript API accepts a key either as a bearer token or in the x-api-key header, per its OpenAPI spec. You get a key from the dashboard or through the self-service signup flow, and one credit is spent per successful request while failed and rate-limited requests are not charged. Through Jentic the key is stored once and injected at call time, so it never enters the agent's prompt or logs.
Can I fetch transcripts for many videos at once with the GetYouTubeTranscript API?
Yes. The batch endpoint queues transcripts for up to 100 videos in a single request and returns a job you can poll for status and a page of results. Combine it with the playlist or channel-videos listing to feed a whole channel into one batch instead of calling the transcript endpoint once per video.
What are the rate limits for the GetYouTubeTranscript API?
The OpenAPI spec does not define numeric rate limits; usage is metered in credits, where one credit is spent per successful request and rate-limited requests are never charged. See https://getyoutubetranscript.com/docs for current limits, and have your agent back off when it receives an HTTP 429 response.
Is there a GetYouTubeTranscript MCP server?
Yes, GetYouTubeTranscript offers an official MCP server. You can also connect the API directly through Jentic: your agent gets the full 13-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.
Can I limit what my agent is allowed to do with the GetYouTubeTranscript API?
Yes. Write a rule that allows only the read operations your workflow needs, such as fetching transcripts and searching videos, so the agent can read captions and metadata but cannot touch the signup or batch-queueing operations unless you add them. Every call it makes is logged.
How do I fetch a transcript through Jentic?
Search Jentic for an intent such as 'get a YouTube video transcript' and it returns the matching transcript operation with its input schema, so your agent passes the video URL or ID and reads back the caption text. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Fetch YouTube video transcripts and caption languages, search videos and channels, resolve channel handles, and list playlist or channel videos. Includes a batch endpoint for up to 100 videos per request.
Use for: Get the transcript of a YouTube video, I want to find which caption languages a video offers, Search YouTube for videos about a topic, Resolve a channel handle to its channel ID
Not supported: Does not upload videos, manage YouTube channels, or run ad campaigns. Use for reading YouTube transcripts, search results, and channel or playlist data only.
The GetYouTubeTranscript API returns the caption transcript of any YouTube video and exposes the surrounding metadata an agent needs to find the right video first. It searches YouTube for videos or channels, resolves a channel handle or URL to a channel ID, lists every video in a playlist or on a channel, and reports a video's available caption languages. Successful requests spend one credit each, failed and rate-limited requests are never charged, and a batch endpoint queues transcripts for up to 100 videos at once.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>