FAQ
Common questions about Onepin — the voice workflow platform for production-ready audio across 100+ TTS models.
What is Onepin?
Onepin is a voice workflow platform that orchestrates, validates, and ships production-ready audio across 100+ TTS models. You build, run, and manage multi-step voice workflows — from source script through translation, generation, and quality validation — and access everything through a REST API, the onepin Python SDK, and the onepin CLI.
Which TTS providers and models does Onepin support?
Onepin runs across 100+ TTS models from leading providers including ElevenLabs, Cartesia, Naver, Respeecher, and Rime, with more added regularly. A single workflow can route different steps to different models. See Voices & Models for details, or run onepin voices list for the live catalog available to your workspace.
What is a voice workflow, and what does “orchestrate” mean?
A voice workflow is a multi-step pipeline that takes a source script and produces finished audio. Onepin orchestrates that pipeline — running steps such as translation, speech generation, and quality validation in order, across whichever TTS models each step needs — so you ship production-ready audio without wiring providers together yourself.
What does “production-ready audio” and validation mean?
Onepin validates generated audio as part of the workflow rather than leaving quality checks to you. The “ship” step produces output that is ready for downstream use, with validation built into the pipeline.
Does Onepin have a Python SDK and a CLI?
Yes. pip install onepin installs both the onepin Python library and the onepin CLI. The SDK offers sync and async clients with typed exceptions and automatic pagination; the CLI exposes the same operations for scripting and CI. See the Python SDK and CLI guides.
How do I authenticate?
Onepin uses API keys (prefixed op_live_). Create one at app.onepin.ai/workspace/~/settings/api, then run onepin login or set ONEPIN_API_KEY. Each key is scoped to a single workspace. See Authentication for the full credential resolution order and scopes.
How do I get started?
Install the SDK, get an API key, and run your first workflow in under 5 minutes — follow the Quickstart.