A transcript preserves words but drops acoustic information. oruk models the transcript, emotion, and speaking style together so applications can use both.
02
Research in the open
We benchmark against the field on its own terms and publish where it counts. Progress you can verify, not claims you have to take on faith.
03
Built for builders
Understanding should be one API call away. We carry the hard parts so the teams shipping conversational AI to real people don’t have to.
Questions
Speech understanding, answered.
What does the oruk API do today?
oruk API v1 processes English audio files for transcription, emotion detection, speaking-style classification, or unified analysis. Unified responses include a transcript, calibrated labels, time-local segments, and tagged text. The current public contract is file based, not streaming.
What speech models does oruk offer?
The API serves two tiers today: Spectra 1 for efficient affect workloads and Resonance, the flagship, for the strongest transcription and unified analysis. Spectra 2 is listed in the catalog as a preview tier but is not yet serving traffic.
How does multilabel emotion detection work?
The API scores 15 emotion labels against thresholds calibrated on held-out audio. A clip may return several emotions. If no emotion crosses its threshold, the highest-scoring emotion is returned as a fallback. Long audio also includes segment-level labels so applications can follow changes over time.
How are speaking styles represented?
Speaking style is a separate 16-label multilabel output. A clip may have multiple styles or no selected style. Emotion and style can be requested independently, together through the affect endpoint, or alongside a transcript through unified analysis.
Is oruk a speech-to-text API?
Yes. Resonance is the recommended model for English transcription. The same API can also return acoustic emotion and speaking-style labels, which preserves useful information that a transcript alone does not contain.
How do developers access oruk?
Developers create an account, which activates immediately with $50 in trial credit, and generate a production API key in the developer portal. The v1 API uses bearer authentication and multipart file uploads. Keys are displayed only once.
Which languages does API v1 support?
API v1 supports English. Inputs may be mono or stereo and use WAV, FLAC, MP3, M4A, OGG, or WebM containers with common sample rates. oruk does not currently advertise multilingual production support for this API.
How is usage billed?
Inference is priced per audio minute and metered by measured second, with a one-second minimum. Each response includes the billable duration, rate, estimated cost, and pricing version. The developer portal shows the immutable credit ledger and request-level usage history.