Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JustTranscribe 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%2Fjusttranscribe.ai%2Fjusttranscribe" | 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%2Fjusttranscribe.ai%2Fjusttranscribe" | 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 JustTranscribe API.
Start transcribing a public video or audio URL up to 150 minutes long, with an optional webhookUrl for completion
Poll a transcript by id as its status moves through stages such as queued, transcribing, and complete
Export a finished transcript as txt, srt, vtt, csv, or md, dropping timestamps with ts=0 or adding speaker labels with sp=1
List past transcripts newest first, filtered by status and sorted by createdAt or completedAt
GET STARTED
Include the plain transcript text in list results with include=text
Permanently delete a transcript by id
Patterns agents use JustTranscribe API for, with concrete tasks.
★ Video Research Through Jentic
An AI agent asked to summarise a public talk starts a JustTranscribe job from the video link, polls the transcript until its status is complete, and reads the text to write the summary. Through Jentic the agent finds the create and get operations by intent and calls them with your API key, which stays on your own machine.
Create a transcript for a public YouTube URL, poll GET /api/v1/transcripts/{id} until status is 'complete', then summarise the text in five bullet points
Subtitle Files for Short-Form Video
A creator repurposing TikTok and Instagram clips needs caption files. The agent transcribes each public link and exports the result as srt or vtt, ready to upload with the video, or as csv when the creator wants to edit segments in a spreadsheet.
Transcribe a public TikTok URL and, once complete, export it with format 'srt' and also as 'vtt'
Content Notes Without Timestamps
A writer turning podcasts and webinars into articles wants clean prose. The agent exports each finished transcript as md with ts=0 to drop timestamps, adding sp=1 when cached speaker labels help attribute quotes.
Export a completed transcript with format 'md', ts '0', and sp '1', then draft an article outline from it
Webhook-Driven Transcription Queue
An app that transcribes many links passes a webhookUrl when creating each transcript, then lists finished jobs sorted by completedAt to pick up anything a webhook missed. This keeps a backlog moving without polling every job individually.
Create transcripts for three public Google Drive video links with a webhookUrl, then list transcripts with status 'complete', sort 'completedAt', and include 'text'
6 endpoints — the justtranscribe api turns public videos and audio into timestamped text from a link.
METHOD
PATH
DESCRIPTION
/api/v1/transcripts
Start transcribing a public URL
/api/v1/transcripts/{id}
Get a transcript and its status
/api/v1/transcripts/{id}/export/{format}
Export as txt, srt, vtt, csv, or md
/api/v1/transcripts
List transcripts
/api/v1/transcripts/{id}
Delete a transcript
/api/v1/transcripts
Start transcribing a public URL
/api/v1/transcripts/{id}
Get a transcript and its status
/api/v1/transcripts/{id}/export/{format}
Export as txt, srt, vtt, csv, or md
/api/v1/transcripts
List transcripts
/api/v1/transcripts/{id}
Delete a transcript
What agents get from Jentic-routed access to this vendor.
Setup
Wiring JustTranscribe by hand means handling its bearer key, the asynchronous create-then-poll flow through statuses like transcribing and complete, and picking export formats and flags. Through Jentic you install once, import the JustTranscribe API from the API Directory, store the key once, and your agent calls it.
Permission scoping
JustTranscribe puts the transcript id in the URL path (/api/v1/transcripts/{id}), so a rule can bound your agent to one transcript and the operations you pick. You choose the operations it may call, so the permanent delete operation is not included unless you add it.
Credential isolation
Your JustTranscribe API 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 'transcribe a YouTube video' or 'export subtitles as srt', and Jentic returns the matching JustTranscribe 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 JustTranscribe API through Jentic.
What authentication does the JustTranscribe API use?
Per its OpenAPI spec, the JustTranscribe API uses bearer authentication with an API key starting with jt_live_, created on the JustTranscribe API keys page and sent in the Authorization header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.
Is there a JustTranscribe MCP server?
You don't need an MCP server to give your agent the JustTranscribe API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, finding the create, poll, and export operations on demand instead of loading a server's tool definitions into its context.
Can I limit what my agent is allowed to do with the JustTranscribe API?
Yes. Write a rule that allows only the create, get, and export operations, so the agent can transcribe and read results but cannot delete anything, and every call it makes is logged. Because the transcript id sits in the URL path, a rule can also pin an agent to one transcript under /api/v1/transcripts/{id}.
Which videos can the JustTranscribe API transcribe?
Per the spec, public links only from YouTube, TikTok, Instagram, Facebook, Pinterest, and Google Drive, up to 150 minutes long. Private or login-required videos are not supported. POST /api/v1/transcripts returns immediately with an id that you poll until status is complete.
What are the rate limits for the JustTranscribe API?
The OpenAPI spec does not specify rate limits. Check https://justtranscribe.ai/developers for current limits and plan details.
How do I transcribe a YouTube video with the JustTranscribe API through Jentic?
Search Jentic for an intent like 'transcribe a YouTube video', import the JustTranscribe API from the API Directory, and store your API key. Your agent calls POST /api/v1/transcripts with the url, polls GET /api/v1/transcripts/{id} until it is complete, then calls the export endpoint with a format such as srt. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Transcribe a public YouTube, TikTok, Instagram, Facebook, Pinterest, or Google Drive video into timestamped text, poll until it is complete, and export it as txt, srt, vtt, csv, or md.
Use for: Transcribe this YouTube video for me, I need subtitles in srt format for a TikTok clip, Get the transcript of a public Instagram reel as plain text, Check whether my transcription job is complete
Not supported: Does not handle private or login-required videos, live streaming transcription, or translation. Use for transcribing public video and audio links and exporting the text only.
The JustTranscribe API turns public videos and audio into timestamped text from a link. It accepts public URLs from YouTube, TikTok, Instagram, Facebook, Pinterest, and Google Drive for media up to 150 minutes long, starts the job asynchronously, and lets you poll the transcript until its status is complete or receive a webhook. Finished transcripts export as txt, srt, vtt, csv, or md, with options to drop timestamps or add speaker labels, and you can list past transcripts or delete one permanently.
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>