Queue it, and let a page make it

If you work with an AI assistant, you can ask it to make sound in AI Audio. One detail is easy to miss, and we would rather you heard it from us.

What your AI can do#

Through Geenius OS your AI gets an audio tool and a collection tool. For sound it can check which providers are ready, queue a run with a kind and a prompt and the options of that kind, list runs and sounds, get one with its waveform, check usage and delete a run with a confirmation. For collections it can list, create and add or remove sounds.

What happens when it queues a run#

The run goes into the history as queued, and the answer includes the credits it costs. The Preview, today's maker, runs in a browser. So a queued run is made as soon as somebody in the workspace has AI Audio open. Your AI cannot make it on its own; it should tell you to open the app and give you the address.

Why a browser#

The Preview synthesises sound in a page and needs no server and no key. That keeps the whole product runnable without a vendor. A real model runs on the server, and once its key is set a queued run is made without anyone watching.

What your AI should say#

That it queued a run, what it costs, that the sound comes from a simulated Preview unless a real model is ready, and which provider is ready. It should not promise a result. Asking for the providers first gives that answer.

Plans#

Making sound needs Premium or Max, whoever asks. The door is on every plan, and a Pro workspace gets the library and nothing queued.

A note on waiting#

A queued run that nobody opens just waits. Nothing is lost: it stays queued until a page claims it, and a page that closes hands the run on to another. If it matters that a run finishes tonight, open the app yourself.

See use with your AI.