Skip to main content

Billing

Kitsch Labs API usage is calculated in credits using service-specific rules. Text to Speech is based on generated audio duration and the voice pricing policy. Noise Reduction and Speech to Text use successfully processed input duration or connection time. See API Pricing for public rates.

How are credits calculated?

Public voice API rates are listed on API Pricing. Actual credit usage can vary by generated output duration and customer contract. Check the current terms for the voice and account before making a request.

Noise Reduction

Successful requests are billed at 1.5 credits per second, rounding the input audio duration up to the next started second. Failed requests and requests rejected during input validation are not charged. Customer-specific contract terms take precedence when applicable.

Speech to Text

API requests use successfully processed input audio duration. The Streaming API uses connection time. Both are rounded up to the next started second and billed at 0.1 credits per second, equivalent to 6 credits per minute. Failed POST requests and requests rejected during input validation are not charged.

What is the difference between prepaid and postpaid?

  • General self-service accounts process requests within their available credits.
  • Enterprise accounts may use postpaid billing and customer-specific rates under their contract.
  • The account and contract determine the billing cycle, currency, taxes, and payment method.

If public documentation or pricing differs from an individual contract, the signed contract and account settings take precedence.

What happens when credits run out?

When a prepaid account has no available credits, the API returns 402 Payment Required.

{
"detail": {
"status": "insufficient_credits",
"message": "Insufficient credits.",
"request_id": "<REQUEST_ID>"
}
}

Automatic retries do not resolve this error. Check the balance, subscription status, or contract limit before sending the request again.

Do purchase features vary by plan?

Additional-credit purchases are planned for Creator and Pro, but customer purchase and automatic top-up features are not currently available. Enterprise terms are set separately by contract. Because prices and included credits can change, do not hard-code pricing in an application. Display the public Pricing page or contract information instead.

Is the rate limit the same as the plan?

No. An API key can have a separate requests-per-minute limit. A common default RPM by tier has not yet been finalized, so implement against the limit provided for the account. When the limit is exceeded, follow the 429 response and Retry-After header.

What should I send with a billing question?

Email the following information to giopaik@kitschlabs.com:

  • Account or company name
  • Billing period to review
  • Related invoice or payment identifier
  • x-kitsch-request-id for the relevant request
  • Difference between the expected and actual amount

Do not include sensitive information such as a raw API key, card number, or security code in the email.