For Agents
Submit audio and video files to GoTranscript for human or AI transcription, captioning, subtitling, translation, and forced alignment, and look up order status by ID.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoTranscript Transcription 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 GoTranscript Transcription API.
Submit a file URL for human-graded transcription with speaker labels and timestamps
Order AI transcription for fast turnaround at lower cost than human jobs
Generate captions or subtitles in multiple supported languages from a media file
Request a translation of an existing transcription into a target language
GET STARTED
Use for: I need to transcribe a one-hour podcast episode, Order AI transcription on a meeting recording, Generate burned-in captions for a marketing video, Translate an English transcript into Spanish
Not supported: Does not handle live streaming transcription, real-time speaker diarization, or audio recording capture — use for batch transcription, captioning, and translation jobs only.
The GoTranscript Transcription API submits audio and video files for human-graded transcription, AI transcription, proofreading, translation, captioning, subtitling, and forced alignment. Orders are placed by POSTing job parameters to dedicated endpoints (such as /transcriptions, /ai-transcriptions, and /captions) and results are returned via callback URLs. The API also exposes language enumeration and order lookup endpoints so clients can validate input options and check job state. Authentication uses an API token passed as the api_token query parameter.
Run forced alignment to match an existing transcript to its source audio
List supported languages and capability codes before placing an order
Look up the state and result location of a previously placed order
Patterns agents use GoTranscript Transcription API for, with concrete tasks.
★ Podcast Transcription Pipeline
Each new podcast episode is published to a storage URL and a transcription job is opened automatically. POST /transcriptions submits the file and the result is delivered to a callback URL once the human or AI transcript is ready. Turnaround depends on tier — minutes for AI, hours to days for human-graded — but the API surface is the same.
Submit https://example.com/episode-42.mp3 for human transcription with English source and request the result at callback URL https://example.com/callbacks/gotranscript.
Video Captioning at Scale
Marketing teams generate burned-in or sidecar captions for video libraries by POSTing each video to /captions or /subtitles. The API accepts the source language and target output format, and returns the deliverable to the callback URL. Useful for pushing accessibility coverage across hundreds of clips without manual upload.
Submit a captioning job for https://example.com/clip.mp4 with English source language and request SRT output to a callback URL.
Multilingual Transcript Translation
Once an English transcript is in hand, /translations creates a target-language version without re-transcribing the audio. This is faster and cheaper than transcribing again from the original file in each language. Common pairing: AI transcription first to get the source text, then human-quality translation for the target language.
Translate transcription order 555 from English into Spanish and return the order ID for the translation job.
AI Agent Transcription Service
An AI agent built on Jentic accepts a URL or file and decides — based on the user's latency and quality requirements — whether to call AI or human transcription. The agent searches Jentic for 'transcribe an audio file', loads the appropriate GoTranscript operation schema, and submits the order without exposing the api_token.
Use Jentic to search 'transcribe an audio file' and submit https://example.com/call.mp3 for AI transcription with English source language.
10 endpoints — the gotranscript transcription api submits audio and video files for human-graded transcription, ai transcription, proofreading, translation, captioning, subtitling, and forced alignment.
METHOD
PATH
DESCRIPTION
/transcriptions
Submit a human-graded transcription order
/ai-transcriptions
Submit an AI transcription order
/captions
Generate captions for a media file
/subtitles
Generate subtitles for a media file
/translations
Translate an existing transcription
/forced-alignment
Run forced alignment between audio and a transcript
/orders
List all orders on the account
/orders/{orderId}
Look up a single order by ID
/transcriptions
Submit a human-graded transcription order
/ai-transcriptions
Submit an AI transcription order
/captions
Generate captions for a media file
/subtitles
Generate subtitles for a media file
/translations
Translate an existing transcription
Three things that make agents converge on Jentic-routed access.
Credential isolation
GoTranscript api_token query secrets are stored encrypted in Jentic's vault. Jentic injects the token into the request URL at execution time, so the secret never appears in the agent's prompt or logs.
Intent-based discovery
Agents search by intent (e.g., 'transcribe an audio file' or 'caption a video') and Jentic returns the right GoTranscript operation with its input schema, so the agent picks AI vs human routes by parameter rather than by URL choice.
Time to first call
Direct GoTranscript integration: 1-2 days for callback handling, retry, and order polling. Through Jentic: under 1 hour to a working transcription submission and order lookup.
Alternatives and complements available in the Jentic catalogue.
Specific to using GoTranscript Transcription API through Jentic.
What authentication does the GoTranscript Transcription API use?
The GoTranscript API uses an API key passed as the api_token query parameter on each request. When called through Jentic, the api_token is stored encrypted in Jentic's vault and is appended to outgoing requests at execution time so the agent never embeds it in code.
Can I order both AI transcription and human transcription with the GoTranscript API?
Yes. POST /ai-transcriptions submits AI-only jobs for fast, lower-cost output and POST /transcriptions submits human-graded jobs. POST /transcription-proofreading submits an AI draft for human review when you want both speed and accuracy.
What are the rate limits for the GoTranscript Transcription API?
Specific rate limits are not declared in the OpenAPI spec. Order submission is typically modest in volume per account, so a small number of concurrent submissions is expected to be safe. Honor HTTP 429 responses with exponential backoff.
How do I submit a transcription job through Jentic?
Search Jentic for 'transcribe an audio file', load the POST /transcriptions operation, and execute with the file URL, source language, and callback URL in the request body. With pip install jentic, the call is a three-step search, load, execute flow.
How do I check the status of a GoTranscript order?
GET /orders/{orderId} returns the state of a single order along with deliverable metadata once the job completes. GET /orders lists orders on the account so an agent can poll for completed jobs without holding individual order IDs.
Does the GoTranscript API deliver results synchronously or by callback?
Results are delivered asynchronously via the callback URL provided in the submission. The POST endpoint returns an order ID immediately, and the deliverable is sent to the callback once transcription, translation, captioning, or alignment completes.
/forced-alignment
Run forced alignment between audio and a transcript
/orders
List all orders on the account
/orders/{orderId}
Look up a single order by ID