LMNT
for LuumenAI
Generate speech, inspect voices, and hold voice changes for approval
Connect LMNT and your agent can read the voice catalog, check a voice's languages and plan availability, and look at account usage before it spends anything. It can synthesize speech from text, with word-level timing when you need it. Changes to voices — creating, updating, deleting — are previewed and approved first.
The LMNT toolbox
8 tools: 5 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGenerate Speech With MetadataGenerates speech from text and returns JSON with base64-encoded audio and optional word-level timing metadata.
- ReadGet AccountRetrieves account information including subscription plan details and current usage statistics.
- ReadGet Voice InfoGets metadata for a specific LMNT voice, including active status, supported languages, and plan availability.
- ReadGet Voices ListRetrieves a list of available voices from LMNT.
- ReadSynthesize SpeechSynthesizes speech from text using LMNT's AI voices.
- WriteCreate VoiceCreates a custom voice in LMNT by training on uploaded audio samples. Approval by default
- WriteDelete Voice InfoDeletes a voice from your LMNT account. Approval by default
- WriteUpdate Voice InfoUpdates information about a specific voice in LMNT. Approval by default
One prompt, start to finish
What a governed LMNT run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create voice, delete voice info, update voice info — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to LMNT — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut LMNT to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.