Trint · Rate Limits

Trint Rate Limits

Trint does not publish fixed numeric per-minute request limits for its REST API. In practice, usage is governed by plan entitlements rather than a documented request cap: the Starter tier enforces a hard monthly file cap (reported around 7 files/month) while Advanced allows unlimited transcriptions. Heavy API consumers are directed to Enterprise. List endpoints such as GET /transcripts/ use limit and skip query parameters for pagination.

Trint Rate Limits is the machine-readable rate-limit profile for Trint on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, files, and items.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Audio Transcription, Transcription, Speech-to-Text, Media, and Rate Limiting.

4 Limits Throttle: 429
Audio TranscriptionTranscriptionSpeech-to-TextMediaRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the REST API.
Starter File Cap account
files
~7 files per month (verify)
Hard monthly cap on Starter with no rollover; effectively bounds transcription throughput.
Advanced Transcription account
files
unlimited (per plan terms)
Advanced allows unlimited transcriptions; heavy API usage is directed to Enterprise.
List Pagination endpoint
items
limit + skip query params
GET /transcripts/ paginates via ?limit=&skip= (documented example limit=100).

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.
Plan-Governed Usage
Effective throughput is bounded by the subscription's file/transcription entitlement rather than a per-second request cap.
Webhook-Driven Polling Reduction
Register webhooks (TRANSCRIPT_COMPLETE, etc.) instead of polling transcript status to reduce request volume.

Sources