i took the ship plan of livekit but it seems to be only working for one project. when i create another project on the same account it shows the free build plan

Thanks for reaching out, Farel. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

okay. now i have two agents on the project in the ship plan. but when i integrate in a mobile app, same websocket url but differnet api key and secret are confused, one agent take the place of another one

Thanks — you're saying two agents in the Ship project, same WebSocket URL, different API keys/secrets, and one agent "takes the place" of the other in your mobile app. I’m responding about that behavior. Short answer: API keys/secrets do not pick or isolate agents. Project credentials and the WebSocket URL are project-scoped, so authentication won’t route to a specific agent. Agent selection is done by agent_name and by how rooms are dispatched. To help you quickly, can you answer these so I can pinpoint the problem? 1. Do both agents have unique

agent_name

values? If so, what are they? 2. Are you using automatic dispatch or explicit dispatch for rooms? (e.g., creating dispatch via the API or including

agents

in the room token) 3. Is your mobile app creating or reusing the same room name/ID for both sessions? 4. Do you see any errors or logs when one agent is replaced? If yes, share the log lines or exact error text. 5. Are both agent processes showing as running in the project (you can check agent status/logs)? If you prefer a quick fix: ensure each agent has a unique

agent_name

and use explicit dispatch (specify

agent_name

when creating the dispatch or in the room token) so the correct agent is assigned to the room. Sources: Agent dispatch | LiveKit docs | Server-side | livekit/livekit_composite | DeepWiki | Quotas and limits | LiveKit docs | Avoiding Room ID Reuse When Re-Creating Rooms With the Same Name