LLM / Controller Readiness
Looking ahead: what an LLM or external controller would need to drive Studio, and where the gaps are.
Coming soon: this is planning only, not built yet. It captures the direction so the API can grow toward it.
At a glance
- What a controller would need from the API.
- Gaps currently being verified.
- Direction, not a shipped feature.
What a controller would need
A controller needs to discover capabilities, submit work, and observe results: list engines/voices, synthesize, and poll jobs, all of which the gateway already covers in basic form.
Current gaps
Richer capability description and status detail are being verified as candidates for the controller surface. Nothing here is committed yet.