Build an agent
You write two things: a brain behind one WebSocket in your backend, and a page that starts a session with one request and your client. An agent record joins them. How Voqalize works explains the parts; the Quickstart gets you to a first session in ten minutes.
The order of work
Section titled “The order of work”- Write the brain. Speech, screen actions, tools, context and history. Bringing logic from another framework instead: Use another agent framework.
- Test the brain. Drive it over the real wire with no microphone and no model, before any session is live.
- Create the agent and say how it is reached. An inbound
wss://route in production, or the Cortex relay from a laptop or a serverless function. - Mint keys. An
sk_for your server; apk_only for a public page. - Connect your app. The
sessions.connectrequest, the response, and the one line of glue. - Pick client libraries. Your client with
@voqalize/client-transport, and the mobile path.
Work with a coding agent does these steps from your editor through the Voqalize MCP server.
Once it works
Section titled “Once it works”- Add voice and language, Stage, the avatar or camera and screen.
- Improve the conversation with Designing for voice.
- Read sessions back and prepare for launch in Operate.