Thanks — you're asking which permissions an ElevenLabs API key needs to run with LiveKit (for the ElevenLabs TTS/STT plugins). I'll answer what we know and point to the next step if you need more detail. Short answer • An ElevenLabs API key is required and must allow access to the ElevenLabs endpoints you plan to use: ◦ TTS generation endpoints if you use ElevenLabs for Text-to-Speech. ◦ STT transcription endpoints if you use ElevenLabs for Speech-to-Text. • You must set the

ELEVEN_API_KEY

environment variable for the LiveKit plugin to use it. What we cannot confirm here • The documentation we have does not list specific named permission scopes (for example, "tts:read" or "stt:write") or a required access level (read-only vs full) for keys used with LiveKit. Recommended next steps 1. If you only need TTS, ensure the key can call ElevenLabs TTS endpoints. If you only need STT, ensure it can call STT endpoints. If you need both, the key must cover both. 2. Check your ElevenLabs account or API key settings for any scope/role controls and enable access to the TTS/STT features. 3. For exact permission names or to confirm whether a restricted/read-only key will work, consult ElevenLabs’ API docs: https://elevenlabs.io/docs/api-reference If you’d like, tell me: • Whether you plan to use TTS, STT, or both — I can then suggest what to check in your ElevenLabs key settings and walk you through setting

ELEVEN_API_KEY

in your environment. Sources: ElevenLabs STT plugin guide | LiveKit Documentation | ElevenLabs TTS plugin guide | LiveKit Documentation