AWS Amazon Transcribe
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentAI/MLSpeechapiKey39 EndpointsREST
For Agents
Transcribe recorded audio to text with optional speaker diarisation, custom vocabulary, redaction, and call-analytics enrichment so an agent can read what was said in a meeting, support call, or clinical encounter.
Use for: I want to transcribe a recorded customer support call, Start a medical transcription job for a clinician dictation, Create a custom vocabulary for product names, Redact sensitive PII from a transcript using a vocabulary filter
Not supported: Does not handle text-to-speech, real-time translation of arbitrary text, or voice cloning — use for converting recorded audio into transcripts (with optional medical or call-analytics enrichment) only.
Jentic publishes the only available OpenAPI specification for Amazon Transcribe, keeping it validated and agent-ready. Amazon Transcribe converts audio into text using automatic speech recognition. It supports three batch transcription modes (Standard, Medical, Call Analytics), custom language models trained on domain-specific text, custom vocabularies for proper nouns, and vocabulary filters for redaction. The 39 operations cover the full lifecycle of transcription jobs, custom vocabularies, language models, and call-analytics categories, plus tagging for cost allocation.
Install Jentic One Beta
Connect the Amazon Transcribe to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Transcribe, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# 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.
Capabilities
What an agent can do with Amazon Transcribe API.
Run batch Standard, Medical, and Call Analytics transcription jobs against audio in S3
Boost accuracy on jargon and proper nouns with custom vocabularies and custom language models
Redact PII or other sensitive terms from transcripts via vocabulary filters
Categorise call recordings against rules in CallAnalyticsCategory definitions
Diarise speakers and surface call sentiment, non-talk time, and interruptions in Call Analytics output
List, describe, and delete jobs, vocabularies, filters, and language models
Tag transcription jobs and resources for cost allocation
Use Cases
Patterns agents use Amazon Transcribe API for, with concrete tasks.
★ Contact-Centre Call Analytics
Run Call Analytics transcription jobs against recorded support calls to get speaker-diarised transcripts with sentiment per speaker, talk-time ratios, non-talk time, interruptions, and category matches against rules you define (e.g. 'mentions cancellation'). StartCallAnalyticsJob accepts an S3 URI, an output location, and a list of CategoryNames; the resulting JSON powers QA dashboards and agent coaching workflows.
Call StartCallAnalyticsJob with CallAnalyticsJobName 'support-2026-06-09-call-42', Media.MediaFileUri s3://calls/2026-06-09/call-42.wav, OutputLocation s3://calls-out/, and ChannelDefinitions for AGENT and CUSTOMER.
Clinical Dictation Transcription
Amazon Transcribe Medical converts clinician dictations into structured text optimised for medical vocabulary. StartMedicalTranscriptionJob accepts the audio, a Specialty (e.g. PRIMARYCARE), a Type (CONVERSATION or DICTATION), and an output bucket; the resulting transcript can be fed into an EHR. The service supports content identification (PHI) for downstream redaction.
Call StartMedicalTranscriptionJob with MedicalTranscriptionJobName, Specialty 'PRIMARYCARE', Type 'DICTATION', Media.MediaFileUri pointing at the dictation audio, and OutputBucketName.
Domain-Specific Custom Vocabularies
Improve recognition of brand names, drug names, or technical jargon by creating a CustomVocabulary (a flat term list) or a CustomLanguageModel (trained on representative transcripts). CreateVocabulary uploads phrases; CreateLanguageModel kicks off training against your S3 training data. Reference the resulting names in StartTranscriptionJob.Settings to apply them to a specific job.
Call CreateVocabulary with VocabularyName 'product-names-v3', LanguageCode 'en-US', and Phrases listing your product catalogue, then reference VocabularyName in subsequent StartTranscriptionJob calls.
Agent-Driven Meeting Note Generation via Jentic
An assistant agent that turns recorded meetings into searchable notes can call Transcribe through Jentic without holding AWS keys. The agent submits an intent like 'transcribe this meeting recording with speaker labels'; Jentic loads StartTranscriptionJob with ShowSpeakerLabels enabled, executes it, and polls GetTranscriptionJob until the TranscriptFileUri is ready. The agent then summarises the transcript with its language model.
Through Jentic, search for 'transcribe an audio file with speaker labels', load StartTranscriptionJob, execute with Media.MediaFileUri, MediaFormat, LanguageCode, and Settings.ShowSpeakerLabels=true.
Key Endpoints
39 endpoints — jentic publishes the only available openapi specification for amazon transcribe, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=Transcribe.StartTranscriptionJob
Start a standard transcription job
POST
/#X-Amz-Target=Transcribe.GetTranscriptionJob
Get transcription job status and transcript URI
POST
/#X-Amz-Target=Transcribe.StartMedicalTranscriptionJob
Start a medical transcription job
POST
/#X-Amz-Target=Transcribe.StartCallAnalyticsJob
Start a Call Analytics transcription job
POST
/#X-Amz-Target=Transcribe.CreateVocabulary
Create a custom vocabulary
POST
/#X-Amz-Target=Transcribe.CreateLanguageModel
Train a custom language model
POST
/#X-Amz-Target=Transcribe.StartTranscriptionJob
Start a standard transcription job
POST
/#X-Amz-Target=Transcribe.GetTranscriptionJob
Get transcription job status and transcript URI
POST
/#X-Amz-Target=Transcribe.StartMedicalTranscriptionJob
Start a medical transcription job
POST
/#X-Amz-Target=Transcribe.StartCallAnalyticsJob
Start a Call Analytics transcription job
POST
/#X-Amz-Target=Transcribe.CreateVocabulary
Create a custom vocabulary
POST
/#X-Amz-Target=Transcribe.CreateLanguageModel
Train a custom language model
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for Amazon Transcribe (used to compute the AWS Signature v4 HMAC in the Authorization header) are held encrypted in the Jentic vault. Agents receive scoped, short-lived execution permissions; the raw access key ID and secret access key never enter the agent's prompt or memory.
Intent-based discovery
Agents call Jentic with an intent like 'transcribe an audio file with speaker labels' and Jentic returns the matching Amazon Transcribe operation along with its input schema, so the agent can invoke the right action without parsing AWS service docs.
Time to first call
Direct integration with Amazon Transcribe: 2-4 days to wire up SigV4 signing, error handling, retries, and IAM scoping. Through Jentic: under an hour — search by intent, load the operation schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Transcribe API through Jentic.
Why is there no official OpenAPI spec for Amazon Transcribe?
AWS does not publish an OpenAPI specification for Amazon Transcribe; it ships Smithy models and language-specific SDKs instead. Jentic generates and maintains this OpenAPI spec so that AI agents and developers can call Amazon Transcribe via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does Amazon Transcribe use?
Transcribe uses AWS SigV4 with X-Amz-Target identifying the action (e.g. Transcribe.StartTranscriptionJob). The IAM principal also needs s3:GetObject on the input audio and s3:PutObject on the output bucket. Through Jentic, your AWS keys are vaulted and Jentic computes the SigV4 signature for each call.
Can I get speaker labels with Transcribe?
Yes. Set Settings.ShowSpeakerLabels=true and Settings.MaxSpeakerLabels in StartTranscriptionJob, or use ChannelDefinitions for stereo recordings where each channel is a known participant. Call Analytics jobs always produce speaker-diarised output with AGENT and CUSTOMER labels.
What are the rate limits for Amazon Transcribe?
Default per-region quotas are typically 100 concurrent batch jobs, audio up to 4 hours and 2GB per file, and a few transactions per second on the management APIs (CreateVocabulary, ListTranscriptionJobs, etc.). Streaming Transcribe has separate connection-level quotas.
How do I transcribe an audio file through Jentic?
Search Jentic with 'transcribe an audio file with speaker labels', load StartTranscriptionJob, and execute with TranscriptionJobName, Media.MediaFileUri, MediaFormat, LanguageCode, and OutputBucketName. Then load GetTranscriptionJob and poll until TranscriptionJobStatus is COMPLETED.
Can Transcribe redact sensitive information from a transcript?
Yes. ContentRedaction.RedactionType=PII removes US PII categories like name, address, and credit card. Custom VocabularyFilters can additionally remove arbitrary terms (e.g. competitor names) by setting Settings.VocabularyFilterMethod to 'mask' or 'remove'.
What languages does Transcribe support?
Standard Transcribe supports more than 30 languages including English variants, Spanish, French, German, Mandarin, Japanese, and Hindi. Medical Transcribe supports US English only. The exact LanguageCode value is required on every transcription job.
GET STARTED