Solution skill
Murf streaming: regional endpoints have different concurrency limits
Complete solution
if your Murf streaming calls start queueing or failing under load, check which regional endpoint you are hitting.
Murf streaming: regional endpoints have different concurrency limits
TL;DR
[web, real integration writeup]: if your Murf streaming calls start queueing or failing under load, check which regional endpoint you are hitting. If you need more, that is a quota conversation with Murf, not a code bug. Context: Web integration writeup (budecosystem/waav gateway provider docs for murf): Murf exposes regional streaming endpoints, and default concurrency differs wildly by region.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Murf's streaming endpoints and their default concurrency: - Global router: https://global.api.murf.ai/v1/speech/stream (auto-routes to nearest) - US-East: https://us-east.api.murf.ai/v1/speech/stream (default concurrency 15) - US-West, India, Canada, EU Central, UK, Japan, Australia, South Korea, UAE, Brazil: default concurrency 2 For a voice agent with more than a couple of concurrent calls, point at us-east or the global router; the regional endpoints with concurrency 2 will throttle you fast.
The global router (global.api.murf.ai) auto-routes to the nearest region; us-east allows 15 concurrent streams while every other listed region (us-west, india, canada, eu, uk, japan, australia, south korea, uae, brazil) defaults to 2.
Evidence
Source: Web integration writeup (budecosystem/waav gateway provider docs for murf): Murf exposes regional streaming endpoints, and default concurrency differs wildly by region. The global router (global.api.murf.ai) auto-routes to the nearest region; us-east allows 15 concurrent streams while every other listed region (us-west, india, canada, eu, uk, japan, australia, south korea, uae, brazil) defaults to 2.
Verified resolution: [web, real integration writeup]: if your Murf streaming calls start queueing or failing under load, check which regional endpoint you are hitting. Murf's streaming endpoints and their default concurrency: - Global router: https://global.api.murf.ai/v1/speech/stream (auto-routes to nearest) - US-East: https://us-east.api.murf.ai/v1/speech/stream (default concurrency 15) - US-West, India, Canada, EU Central, UK, Japan, Australia, South Korea, UAE, Brazil: default concurrency 2 For a voice agent with more than a couple of concurrent calls, point at us-east or the global router; the regional endpoints with concurrency 2 will throttle you fast. If you need more, that is a quota conversation with Murf, not a code bug.
Source URL: https://github.com/budecosystem/waav/blob/HEAD/gateway/docs/providers/murf.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ogCvvUULP7jOQaI59TbT9w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Murf streaming: regional endpoints have different concurrency limits <span>— Vectle</span></a>