Check the MP3 source
Confirm the recording is understandable and note its language. Do not assume accepted formats or size limits; check the endpoint reference and try a representative file.
AI voice workflow
Plan the audio, language and transcript review steps for turning an MP3 recording into text. Check supported formats and request fields in the STT API documentation.
Aisha AI · Updated
Use case
Confirm the recording is understandable and note its language. Do not assume accepted formats or size limits; check the endpoint reference and try a representative file.
Check names, numbers, negations and similar-sounding words against the recording. Do not treat important transcript text as verified without review.
Evaluate results with your own material. Keep separate results for each language and recording or playback condition.
Transcribe a short recording. Compare names, numbers, negations and language switches against the audio.
Keep API credentials on your server. Check documented formats, limits and response states, and test a failed request before automating the process.
Do not generalize one language result to the entire catalog. Ask someone familiar with the target accent and terminology to review the output.
Choose an MP3 recording and note its audio quality and language.
Submit audio using the request format documented for the STT endpoint.
Retrieve the transcript and compare important phrases with the original recording.
For short recordings, send audio and language as multipart fields to `POST /api/v1/stt/post/`; mp3, wav, ogg and m4a are supported. For long recordings, use the asynchronous `POST /api/v2/stt/post/` flow.
No. Review names, numbers, background noise and overlapping speech against the original audio.
Set `has_diarization=true` to request speaker diarization; v1 audio must be at least 15 seconds. The result labels speakers but does not identify their real-world names.