audio.transcribe.submit
Submit an audio file URL for speech-to-text transcription. Returns a transcript_id to check status and retrieve results. Supports MP3, WAV, M4A, FLAC, OGG, WebM. 99 languages auto-detected. Optional speaker diarization (AssemblyAI)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/audio.transcribe.submit.md
What audio.transcribe.submit does on Apibase
AI agents invoke audio.transcribe.submit to trigger actions in Apibase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Speech model: "universal-2" (default, fast, 99 languages) or "universal-3-pro" (highest accuracy, promptable) |
audio_url | string | Yes | Publicly accessible URL of the audio file to transcribe (MP3, WAV, M4A, FLAC, OGG, WebM) |
language_code | string | — | Language code (e.g. "en", "es", "de", "fr", "ja"). Auto-detected if omitted |
speaker_labels | boolean | — | Enable speaker diarization — detect who said what (default false) |
Parameters from the server's own tool schema.
Why audio.transcribe.submit is rated High
Triggers an external transcription job on a third-party service with ongoing processing.
From the tool's definition Submit an audio file URL for speech-to-text transcription
Attacks that exploit this kind of access
The rule that runs audio.transcribe.submit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audio.transcribe.submit, this is the rule to start with:
audio.transcribe.submit stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every audio.transcribe.submit call is checked against it from then on.
Questions about audio.transcribe.submit
Submit an audio file URL for speech-to-text transcription. Returns a transcript_id to check status and retrieve results. Supports MP3, WAV, M4A, FLAC, OGG, WebM. 99 languages auto-detected. Optional speaker diarization (AssemblyAI). It is categorised as a Execute tool in the Apibase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
audio.transcribe.submit accepts 4 parameters: model, audio_url, language_code, speaker_labels. Required: audio_url. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for audio.transcribe.submit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
audio.transcribe.submit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the audio.transcribe.submit rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for audio.transcribe.submit. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
audio.transcribe.submit is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue