tts-1 API
tts-1 from OpenAI is an audio service in the catalogue. Text to speech and speech recognition are different tasks; confirm the model’s task and supported audio format before integrating.
PreparingService type
Sale prices will appear after provider configuration is complete.
- API model ID
- gapgpt-tts-1-d1c63ad43a
- Model developer
- OpenAI
- Service type
- Audio
- Current availability
- Preparing
Model features
No additional gateway capabilities have been confirmed for this model.
What is tts-1?
Use the public identifier gapgpt-tts-1-d1c63ad43a for tts-1 in ServerNet. The gateway uses this identifier to select the configured route; the developer is OpenAI.
For tts-1, compare pronunciation, voice selection and audio format. Speech generation needs a character or other confirmed native billing bound.
Where to use tts-1
- Check whether tts-1 synthesizes speech or transcribes audio.
- Evaluate pronunciation or transcription quality with a representative sample.
- Check audio duration, output format and supported voices or languages for your application.
Build your integration
Audio execution needs explicit text or file limits and a verified native endpoint. Use the documented route once it becomes available; a text chat request does not perform an audio task.
Inputs and service limits
Character, duration and generation limits differ between audio models. Voice conditioning and uploaded audio can add consumption. Supported languages and voices must come from the model’s confirmed contract.
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
Frequently asked questions
Is tts-1 available through ServerNet?
tts-1 is currently unavailable for API use. A catalogue listing does not activate billing or access. Choose an available related model or check this page again after the route is verified.
Which model ID and API endpoint should I use for tts-1?
This model needs a native execution route. A chat, embedding or reranking example would not execute the advertised task. Its public page remains a catalogue reference until the route and metering are ready.
How is tts-1 usage charged?
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
What should I check before using tts-1 in production?
Character, duration and generation limits differ between audio models. Voice conditioning and uploaded audio can add consumption. Supported languages and voices must come from the model’s confirmed contract.