Comment on: Parrot Speech-to-text API

Building a dedicated validation layer for Hindi downstream workflows is clever. Most generic STT APIs fall apart on code-switching and regional accents. We've hit similar walls where raw transcripts were too noisy for reliable intent parsing in production pipelines. How do you handle Hinglish code-switching, and what's the P95 latency on a 10-second audio chunk?