Going to production
Work down the list before launch. Each line links the page that owns it.
Keys and access
Section titled “Keys and access”- Start sessions from your server with an
sk_key. Use apk_only on a public page, and never in a native app, which sends noOrigin. Connect your app - List every production origin on each
pk_, and only those. Keys and authentication - Know how you will rotate a key: mint, redeploy, then revoke the old one. Practise it once. Rotating a key
- Grant members the narrowest role, and remember
add_membergrants access at once. MCP server
The brain
Section titled “The brain”- Serve an inbound
wss://route behind your TLS and load balancer, and set it as the agent’sbrain_url. Use Cortex in production only for serverless or egress-only brains. Deploy the brain - Verify the brain-connection token, which
run_sessiondoes by default. Never setallow_unverified=Trueoutside local development. The brain-connection token - Pin exact versions of
voqalize-agent-sdkon your server and@voqalize/client-transportin your page. Versions - Handle
on_error, and logoverloadso you know when a queue is shedding frames. Error codes - Run the conformance suite in CI, plus your own scenarios, so a broken turn fails a build rather than a session. Test the brain
Data and consent
Section titled “Data and consent”- Decide
recordfrom the user’s consent, per session, on your server. Recordings - Send identifiers, not personal data, in
init: it is stored on the session. Context and history - Check region and retention fit your obligations. Sessions are processed and stored in India today. Status and support
- Download any recording you must keep before retention ends. Status and support
Limits
Section titled “Limits”- Plan for the one-hour session cap: a session ends with
max_durationat the hour. Usage and limits - Know that a live call cannot be stopped from outside it. Archiving the agent or revoking its key refuses new sessions; calls already connected run until the caller or your brain ends them, or the hour cap does. To end one yourself, close the brain’s socket for that session.
- Ask us about concurrency and minutes if launch traffic may exceed your plan. Usage and limits
After launch
Section titled “After launch”- Alert on the gap between
sessions_createdandsessions_started: a wide gap is a broken embed. Usage and limits - Read a sample of sessions back each week, the call record first,
including
never_spokenunits and gaps. Reading a call back - Log the
session_idon your side withconfigure_loggingor your own loguru format, so both halves of a session join. Reading a call back
Read next
Section titled “Read next”- Troubleshooting: when something goes wrong anyway.
- Usage and limits: what is counted.
- Status and support: region, retention and support.