Routing

Regional Routing

Overview

(Beta)

Regional Routing on slng.ai allows customers to direct their Text-to-Speech (TTS) and Speech-to-Text (STT) requests to specific geographic regions. This supports both data compliance and latency-sensitive use cases — giving you full control over where your audio data is processed and served.

Whether you're building voice features for a regulated industry (e.g. healthcare or finance), or optimizing for low-latency in real-time applications, regional routing ensures your requests stay local and fast.

Key Features

• Region-Specific Execution
• Latency Optimization
• Jurisdictional Compliance
• Org-Level Default Region
• Request-Level Region Overrides
• Fallback-Aware Smart Routing

---

How It Works

slng.ai operates infrastructure across multiple global regions. When you set a region, we guarantee that:

1. Your request will only be handled by models hosted in that region.
2. Your data will not leave the selected region during inference.
3. If no models are available in that region, we return an error unless fallback is enabled.

Supported Regions (Growing)

Region Code	Location Description
EU	European Union (e.g., Frankfurt)
us-west	Western USA (e.g., Oregon)
us-east	Eastern USA (e.g., Virginia)
asia	Asia Pacific (e.g., Singapore)
me	Middle East (e.g., Dubai, beta)

---

Example Request

Code(json)
 
POST /tts
Content-Type: application/json

{
  "text": "Run this in Europe only.",
  "language": "en-GB",
  "region": "EU"
}

Sample cURL

Code(bash)
 
curl -X POST https://api.slng.ai/tts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Run this in Europe only.",
    "language": "en-GB",
    "region": "EU"
  }'

---

Request Parameters (Regional Routing)

Field	Type	Description
region	string	The region where the request should be executed. Example: EU, us-west
fallback_if_unavailable	boolean (optional)	If true, will fall back to the best global model if none is available in region. Default is false.

---

Use Cases

• 🛡 Compliance: Keep voice data within regulated zones (e.g., GDPR, HIPAA)
• ⚡️ Latency: Serve real-time speech apps with region-local infrastructure
• 🌍 Sovereignty: Route voice traffic for users in specific countries or enterprises

---

Best Practices

• Set an org-wide default region via the dashboard
• Use request-level region overrides for specific latency/compliance use cases
• If strict compliance is required, keep fallback_if_unavailable set to false

---

Known Limitations (Beta)

• Some voice models are only available in select regions
• Regional capacity may fluctuate based on GPU load
• Cloning may be restricted in certain jurisdictions

---

Quick Links

• Get API Key
• Available Models per Region
• Compliance Statement
• Smart Routing

---

Last updated: June 2025