Can Lyro generate audio through AiVOOV?

No. The toolkit exposes one action, List Voices, so Lyro can tell you which voices exist and return the voice_id each one needs, but the audio itself is produced in AiVOOV. Lyro's part here is identifying the voice, not synthesising the file.

Is there a limit on how often Lyro can call this?

Yes. List Voices is rate limited to 20 calls per day, which is why the result is worth caching rather than re-fetching for every conversation. A voice catalogue changes rarely, so a single pull usually covers a day of questions.

Can Lyro narrow the catalogue to one language?

Yes, using the language_code parameter. That matters on a catalogue of this size: without a filter the response is the full list of voices, and with one it is the handful actually usable for the language you are producing audio in.

Can Lyro hand a chosen voice to another tool?

Yes. The voice_id that List Voices returns is the identifier AiVOOV needs in order to create audio, and Lyro can pass it to another connected integration in the same conversation rather than the two systems being joined by a prebuilt automation.

Aivoov MCP integration

Reads the available voice catalogue, returning each voice_id, name, gender, and language, and narrows it to one language code on request.

Connect Aivoov See all integrations

1actions available

What your agent can do with Aivoov

Every action runs live through MCP. Nothing to build, nothing to maintain.

List voices
Lyro fetches available text-to-speech voices from AiVOOV to choose the right one for customer responses. This ensures consistent, professional audio delivery across interactions.

See all 1 actions

How businesses use Aivoov + Lyro

Each card is one request a support team gets, and the Aivoov actions Lyro runs to close it.

Find the right voice for a language
Lyro reads the AiVOOV voice catalogue and narrows it to the language code that was asked about, instead of anyone scrolling a dashboard list.
List VoicesFilter By Language Code
Hand over the voice_id that is actually needed
Each entry carries its voice_id, so Lyro returns the identifier required to generate audio rather than just the voice's name.
List VoicesRead Voice Id
Answer which voices exist at all
When someone asks whether a language or a gender is covered, Lyro checks the live catalogue and answers from what it returns.
List VoicesCheck Language Coverage
Pick the voice as one step of a bigger request
Where audio is one part of a longer task, Lyro resolves the voice from the catalogue and carries on with the rest of the conversation.
List VoicesRead Voice Id

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Aivoov actions it has and picks the ones a request needs.

01
Connect Aivoov
Authorize the Aivoov account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Aivoov actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Aivoov · Lyro

Everything else about Aivoov

Setup, permissions, and the limits of what Lyro can do inside Aivoov.

No. The toolkit exposes one action, List Voices, so Lyro can tell you which voices exist and return the voice_id each one needs, but the audio itself is produced in AiVOOV. Lyro's part here is identifying the voice, not synthesising the file.