Skip to main content

​
Credit-based quota

Usage is metered in credits, drawn from a single balance shared by TTS and ASR — there is no separate per-service quota and no billing cycle to reset. One credit is ₹1, and buys 1,000 characters of speech or 100 seconds of audio; see Pricing. When your balance cannot cover a request, it returns 402 until you top up.

​
Checking usage

Query your current usage with:
The response carries your live balance at data.credits.remaining. Check it proactively before large batches so you can top up or throttle before hitting 402.

​
Rate limiting

Beyond quota, the API rate-limits bursts of requests. If you send too many too quickly you’ll get 429:
Handle it with exponential backoff (see Errors). For high throughput, queue requests and cap concurrency rather than firing them all at once.
Exact per-second/per-minute rate-limit thresholds depend on the deployment. Design for backoff on 429 rather than a fixed request rate.