Hume Text-to-Speech

Name: Hume Text-to-Speech API
Brand: Hume Text-to-Speech
Availability: InStock

✓ Official Vendor SpecAI/MLSpeechbearer8 EndpointsREST

For Agents

Synthesise emotionally expressive speech from text in batched or streaming form, manage saved voices, and convert audio between voices.

Install Jentic One Beta

Connect the Hume Text-to-Speech to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Hume Text-to-Speech API.

Synthesise expressive speech from text and return the audio as JSON

Synthesise speech and stream the audio bytes directly to the caller

Stream synthesis as JSON chunks for low-latency rendering

GET STARTED

Start building with Hume Text-to-Speech API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Hume Text-to-Speech API for, with concrete tasks.

★ Studio-quality narration for video and podcast

Turn a written script into expressive narration for a video or podcast using a saved branded voice. The file synthesis endpoint returns a complete audio asset suitable for direct upload into the editing pipeline, while the JSON variant lets the caller inspect timestamps and segment the result before rendering.

Call POST /v0/tts/file with the script text and the saved voice ID to receive the rendered audio file ready for the editor.

Real-time voice for conversational agents

Stream Hume TTS output as it is generated so a conversational agent can speak natural responses without waiting for full synthesis. The streaming JSON endpoint emits chunks the client renders progressively, cutting perceived latency on long replies.

Call POST /v0/tts/stream/json with the agent's reply text and pipe the chunks to the audio renderer as they arrive.

Voice cloning and voice conversion

Convert an existing audio clip — a voice memo, an old recording, or another TTS output — into a different voice while keeping the original timing and inflection. Combined with the saved-voice library, this lets a team standardise on a brand voice across legacy assets without re-recording.

Call POST /v0/tts/voice_conversion/file with the source audio and the target voice ID to receive the converted audio.

Agent-driven narration through Jentic

An AI agent producing automated content searches Jentic for the Hume synthesis operation, loads the schema, and renders a script in the chosen voice. Jentic injects the Hume Bearer token from the vault so the agent never holds the raw credential.

Through Jentic, search 'synthesise speech with Hume', load the schema for POST /v0/tts/file, and execute it with the script text and target voice ID.

Key Endpoints

8 endpoints — hume's text-to-speech api, powered by the octave model, synthesises emotionally expressive speech from text and supports both batched and streaming output.

METHOD

PATH

DESCRIPTION

POST

/v0/tts

Synthesise speech and return the audio in JSON

POST

/v0/tts/file

Synthesise speech and return a downloadable audio file

POST

/v0/tts/stream/json

Stream synthesis as JSON chunks

POST

/v0/tts/stream/file

Stream synthesis as audio bytes

GET

/v0/tts/voices

List saved voices on the account

POST

/v0/tts/voices

Save a new voice to the account library

DELETE

/v0/tts/voices

Delete a saved voice from the library

POST

/v0/tts/voice_conversion/file

Convert an audio file to a different voice

POST

/v0/tts

Synthesise speech and return the audio in JSON

POST

/v0/tts/file

Synthesise speech and return a downloadable audio file

POST

/v0/tts/stream/json

Stream synthesis as JSON chunks

POST

/v0/tts/stream/file

Stream synthesis as audio bytes

GET

/v0/tts/voices

List saved voices on the account

Why Jentic?

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

Credential isolation

Hume API keys are stored encrypted in the Jentic MAXsystem vault. Agents call TTS operations through scoped execution handles so the raw Bearer key never enters the agent's prompt context.

Intent-based discovery

Agents search by intent like 'synthesise speech' or 'convert this voice' and Jentic returns the matching Hume operation with its input schema, including text payload, voice ID, and streaming options.

Time to first call

Direct integration: 1-2 days for auth, voice library management, and streaming chunk handling. Through Jentic: under 30 minutes — search, load, execute the synthesis operation.

FAQs

Specific to using Hume Text-to-Speech API through Jentic.

What authentication does the Hume TTS API use?

It uses Hume API keys passed as a Bearer header. Through Jentic the key is held in the encrypted MAXsystem vault and injected at execution time so the synthesis agent never sees the raw credential.

Can I stream audio for low-latency playback?

Yes. POST /v0/tts/stream/file streams audio bytes directly to the caller, and POST /v0/tts/stream/json streams synthesis as JSON chunks suitable for progressive client-side rendering.

What are the rate limits for the Hume TTS API?

Hume applies per-key rate limits that scale with the account tier; concurrency on streaming endpoints is also tier-bound. Check the Hume dashboard for the active project's quota before scaling parallel synthesis.

How do I synthesise speech through Jentic?

Search Jentic for 'synthesise speech with Hume', load the schema for POST /v0/tts/file, and execute it with the script text and target voice ID. Jentic returns the rendered audio as a binary payload.

Can I save and reuse a custom voice?

Yes. POST /v0/tts/voices saves a voice to the account library and returns a voice ID that can be referenced on subsequent synthesis calls. GET /v0/tts/voices lists existing entries and DELETE /v0/tts/voices removes them.

Does the API perform speech-to-text or transcription?

No. This API synthesises speech from text and converts existing audio between voices. For transcription, use a dedicated speech-to-text provider such as Deepgram or AssemblyAI.

Hume Text-to-Speech

Connect the Hume Text-to-Speech to your agent

Capabilities

Start building with Hume Text-to-Speech API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs