Genny by LOVO Text-to-Speech API

Name: Genny by LOVO Text-to-Speech API API
Brand: Genny by LOVO Text-to-Speech API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLSpeechapiKey5 EndpointsREST

For Agents

Generate text-to-speech audio with LOVO voice speakers using sync or async jobs, list available voices, and check team billing status.

Connect the Genny by LOVO Text-to-Speech API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Genny by LOVO Text-to-Speech API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Genny by LOVO Text-to-Speech API API.

List the available LOVO speakers with their language, gender, and style metadata

Generate synchronous TTS audio for short text under tight latency constraints

Submit asynchronous TTS jobs for longer scripts and poll for completion

Retrieve a finished TTS job's audio URL by job ID before the 24-hour expiry

GET STARTED

Start building with Genny by LOVO Text-to-Speech API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Genny by LOVO Text-to-Speech API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Genny by LOVO Text-to-Speech API, keeping it validated and agent-ready. Genny by LOVO is a text-to-speech service offering both synchronous and asynchronous generation against a catalogue of voice speakers across many languages and styles. The API exposes speaker discovery, sync and async TTS jobs, job-status polling, and team billing context. Generated audio URLs expire 24 hours after creation, so consumers should download or rehost output before the link expires.

Use Cases

Patterns agents use Genny by LOVO Text-to-Speech API API for, with concrete tasks.

★ Voiceover Production for Video

Video producers and creator-tool platforms need voiceovers across many languages and styles without booking studio time. Genny offers a catalogue of LOVO speakers and async TTS jobs sized for full scripts; producers submit a script via /api/v1/tts, poll /api/v1/tts/{jobId} for completion, and pull the audio URL into their editing pipeline within minutes.

List speakers via /api/v1/speakers, pick a US English narrator, submit a 1500-word script via /api/v1/tts, then poll /api/v1/tts/{jobId} every 5 seconds for the audio URL

Real-Time IVR Prompts

IVR and voicebot platforms regenerate menu prompts and confirmation messages on demand. The /api/v1/tts/sync endpoint returns audio for short text inputs in a single call, so an agent can generate 'Press 1 for billing' style prompts at deploy time or render dynamic confirmations like order numbers during a live call.

Call /api/v1/tts/sync with the dynamic phrase 'Your order 48291 ships tomorrow' and return the audio bytes to the IVR runtime

Localised Onboarding Audio

SaaS products onboarding non-English users localise welcome and tutorial audio across many target languages. By iterating /api/v1/speakers to pick a regional voice and submitting scripts via /api/v1/tts, teams ship audio for ten or more locales at a fraction of the cost of voice talent — and refresh it whenever the script changes.

For each target locale, find a matching speaker via /api/v1/speakers and submit the localized welcome script via /api/v1/tts

AI Agent Audio Asset Builder

An AI agent assembling a podcast, audiobook, or training-course audio track can drive Genny end-to-end. Through Jentic the agent searches for 'generate text-to-speech', loads the relevant TTS schema, and executes the call. The X-API-KEY stays in the Jentic vault and the agent simply receives the finished audio URL.

Search Jentic for 'generate text-to-speech', list speakers, choose a narration voice, submit the chapter script via /api/v1/tts, and return the audio URL once the job completes

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for genny by lovo text-to-speech api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/teams/status

Retrieve team billing status and plan information

GET

/api/v1/speakers

List available LOVO speakers

POST

/api/v1/tts/sync

Generate TTS audio synchronously for short inputs

POST

/api/v1/tts

Submit an asynchronous TTS job for longer scripts

GET

/api/v1/tts/{jobId}

Retrieve the status and audio URL for a TTS job

GET

/api/v1/teams/status

Retrieve team billing status and plan information

GET

/api/v1/speakers

List available LOVO speakers

POST

/api/v1/tts/sync

Generate TTS audio synchronously for short inputs

POST

/api/v1/tts

Submit an asynchronous TTS job for longer scripts

GET

/api/v1/tts/{jobId}

Retrieve the status and audio URL for a TTS job

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LOVO X-API-KEY values are stored encrypted in the Jentic vault and injected into outgoing requests at execution time. Agents call TTS operations by name and never see the raw key.

Intent-based discovery

Agents search by intent ('generate text-to-speech') and Jentic returns the matching Genny operation with its parameter schema — speaker selection, text input, and output format — so the agent calls the right endpoint without parsing LOVO docs.

Time to first call

Direct LOVO integration: 1-3 days for auth, async job polling, and audio URL handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ElevenLabs

Realistic AI voice generation with voice cloning and emotional control

Choose ElevenLabs when you need ultra-realistic prosody, voice cloning, or emotion control beyond LOVO's catalogue voices

Complementary

Deepgram

Speech-to-text and audio intelligence — pair with LOVO for full voice-in / voice-out flows

Use Deepgram alongside LOVO when building a voice agent that must transcribe user speech and respond with synthesised audio

Complementary

OpenAI

Generate the script with GPT, then synthesise the audio with LOVO

Pair OpenAI for script generation with Genny for voice rendering when assembling end-to-end voice content

FAQs

Specific to using Genny by LOVO Text-to-Speech API API through Jentic.

Why is there no official OpenAPI spec for Genny by LOVO Text-to-Speech API?

LOVO does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Genny by LOVO Text-to-Speech API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Genny by LOVO TTS API use?

Genny uses an API key sent in the X-API-KEY header on every request. Through Jentic the key is stored encrypted in the vault and attached to outgoing calls at execution time, so an agent calling /api/v1/tts never handles the raw secret.

When should I use sync vs async TTS endpoints?

Use POST /api/v1/tts/sync for short inputs where you need the audio bytes back in a single call (IVR prompts, dynamic snippets). Use POST /api/v1/tts plus polling on /api/v1/tts/{jobId} for full scripts, narration, or any input long enough that a single-request timeout is a risk.

How long are the audio URLs valid?

Audio URLs returned by the TTS endpoints expire 24 hours after the job completes. Download or rehost the file before the expiry — re-fetching /api/v1/tts/{jobId} after expiry will not return a usable link.

What are the rate limits for the Genny TTS API?

The OpenAPI spec does not declare explicit per-second rate limits. Usage is bounded by the team's character allowance, which you can inspect via GET /api/v1/teams/status before submitting a large batch.

How do I generate a voiceover from a script through Jentic?

Run pip install jentic, search Jentic for 'generate text-to-speech', list speakers via /api/v1/speakers, then submit the script via /api/v1/tts and poll /api/v1/tts/{jobId} for the finished audio URL. Jentic injects the X-API-KEY for you.