Official vendor OpenAPI document · agent-readyAI/MLSpeechbearer18 EndpointsREST
For Agents
Transcribe audio and video, read transcripts with speakers and timings, translate them, and ask questions across recordings. Returns structured JSON over a bearer-authenticated REST API.
Use for: I want to transcribe an uploaded audio file, Import a recording from a public link and transcribe it, Get the transcript with speaker labels for a note, Translate a transcript into Spanish
Not supported: Does not host live calls, generate speech from text, or edit the source media. Use for transcribing, analysing, and querying recorded audio and video only.
The AudioMap API transcribes audio and video, then lets you read, analyse, and query the result programmatically. It imports media from a public link or a direct upload, returns transcripts with segments, speaker labels, and word timings, and can translate them into other languages. From a transcript it generates analyses, chapter outlines, question answers over one or all notes, and written deliverables.
Install Jentic One Beta
Connect the AudioMap API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AudioMap 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.
1
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%2Faudiomap.ai%2Faudiomap" | sh2
Step 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%2Faudiomap.ai%2Faudiomap" | 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 AudioMap API.
Transcribe audio and video from a public link or a direct upload
Return transcripts with segments, speaker labels, and word timings
Translate a transcript into another language
Generate analysis templates and chapter outlines for a note
Answer questions about one note or across every note you own
Write documents and deliverables from a note's content
Use Cases
Patterns agents use AudioMap API for, with concrete tasks.
★ AI Agent Transcription Integration via Jentic
An agent that works with recordings can call AudioMap through Jentic without wiring the bearer key or managing the upload-and-poll flow. The agent searches by intent, receives the operation schema, imports or uploads media, and reads the transcript back as structured JSON. This fits meeting assistants, media pipelines, and research tools that turn speech into text they can act on.
Search Jentic for 'transcribe an audio file', load the operation schema, import the recording, and read back the transcript
Audio and Video Transcription
Turn a recording into text with segments, speaker labels, and word-level timings. AudioMap accepts a public link or a direct upload, processes it, and returns a transcript an agent can parse, caption, or index. Translation into another language is available on the same transcript.
Call POST /v1/notes to import a recording, then GET /v1/notes/{id}/transcript to read the transcript
Transcript Q&A and Search
Ask natural-language questions about a single recording or across every recording you own, with answers grounded in the transcripts rather than invented. This lets a research or support agent pull a specific fact from one call, or find which recordings mention a topic across a library.
Call POST /v1/notes/{id}/ask with a question to get an answer grounded in one note's transcript
Deliverable Generation from Recordings
Produce written outputs such as summaries or structured documents directly from a note's content. An agent can generate a meeting recap or an analysis template from a transcript, then list the deliverables created for that note for follow-up.
Call POST /v1/notes/{noteId}/deliverables to write a summary document from a note
Key Endpoints
18 endpoints — the audiomap api transcribes audio and video, then lets you read, analyse, and query the result programmatically.
METHOD
PATH
DESCRIPTION
POST
/v1/notes
Import from a link or open a direct upload
GET
/v1/notes
List notes, newest first
GET
/v1/notes/{id}/transcript
Get the transcript with segments and speakers
POST
/v1/notes/{id}/transcript/translation
Translate the transcript into a language
POST
/v1/notes/{id}/analysis
Generate or regenerate an analysis template
POST
/v1/notes/{id}/ask
Ask a question about one note
POST
/v1/ask
Ask a question across every note you own
POST
/v1/notes/{noteId}/deliverables
Write a document from the note
POST
/v1/notes
Import from a link or open a direct upload
GET
/v1/notes
List notes, newest first
GET
/v1/notes/{id}/transcript
Get the transcript with segments and speakers
POST
/v1/notes/{id}/transcript/translation
Translate the transcript into a language
POST
/v1/notes/{id}/analysis
Generate or regenerate an analysis template
POST
/v1/notes/{id}/ask
Ask a question about one note
POST
/v1/ask
Ask a question across every note you own
POST
/v1/notes/{noteId}/deliverables
Write a document from the note
Jentic AI Readiness Score
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.
A
AudioMap API
- AI-Aware (B)65/100
82
Foundational Compliance66
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability60
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
66
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
9%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
56%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
36%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AudioMap API by hand means managing its bearer key, uploading or importing media, polling until processing finishes, and shaping transcript, analysis, and ask requests yourself. Through Jentic you install once, import AudioMap from the API Directory, store the key once, and your agent calls it.
Permission scoping
AudioMap puts the note id in the URL path (/v1/notes/{id}/...), so a rule can pin your agent to the note operations you pick. You choose the operations it may call, so you can allow transcript reads and questions while leaving new uploads and translation writes out.
Credential isolation
Your AudioMap 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 recording' or 'ask about a note', and Jentic returns the matching AudioMap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AudioMap API through Jentic.
Is there an AudioMap MCP server?
You don't need a separate MCP server to give your agent the AudioMap API. Jentic connects it directly from the API Directory: import it, store your bearer key once, and your agent calls the transcription, translation, and ask operations it needs.
Can I limit what my agent is allowed to do with the AudioMap API?
Yes. Write a rule that allows reading a note's transcript and asking questions about it under one note id, so the agent can read and query that recording while importing new media or starting a translation stays out of reach. Every call is logged by your self-hosted instance.
What authentication does the AudioMap API use?
The AudioMap API authenticates with a bearer API key sent in the Authorization header, per its OpenAPI spec. A session JWT is not accepted; the REST API expects an API key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I ask questions about a recording with the AudioMap API?
Yes. After a note is transcribed you can ask a question about that single note, or ask across every note you own, and AudioMap answers grounded in the transcripts. It also generates analyses, outlines, and written deliverables from the same content.
What are the rate limits for the AudioMap API?
The OpenAPI spec does not specify rate limits, though the REST API is available from the Pro plan up and a lower-plan call returns a 403 with the required tier. Check the vendor's documentation at https://audiomap.ai for current limits and plan tiers.
How do I transcribe a recording with the AudioMap API through Jentic?
Search Jentic for 'transcribe an audio file' and it returns the AudioMap import operation with its input schema; supply a link or upload and the agent reads the transcript back as structured JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED