pricing
tts is prorated for the exact submitted
text character count. whitespace,
punctuation, newlines, and inline tags count; mulberry’s description does not.
for rest-of-world accounts, the canonical inr tts price is converted with
silk’s current shared inr exchange-rate snapshot. agents remain billed from
server-measured call milliseconds. audio milliseconds are recorded for tts
telemetry but never determine a payg tts charge. payg requests use the
plan’s usage-based pricing; api requests never buy capacity automatically.
account-wide capacity
capacity belongs to the account, not an api key, project, voice, or model. mulberry, muga, and agents all draw from the same four request slots. if all slots are busy, silk fails fast with http429, code
concurrency_limit_exceeded, and the active count plus the account limit.
usage is available on the dashboard.
ready to build?
get an api key
create a key and make your first request in the quickstart.