API usage & cost

LIVE
Top panel = real billing pulled live from Twilio & Mobile Message. Below it = self-instrumented ledger of the concierge stack ($ are estimates from editable rates in the worker). Updates every 30s.

Share a demo link tracked

Pick a demo, set a tag (defaults to today's date — change to a name for per-person tracking), copy. Opens of that link show up tagged in "Demo opens" below; your own devices stay excluded.
Loading…

Cost caps & insurance
Live in all widgets — idle auto-end, per-session hard caps & 5 re-opens/day, with a ?dev=sozou-ok bypass for your own testing. Tune via cfg.caps in init.

The caps

These are LIVE now (demo-tight, since you're sending to one colleague). "Live (production)" = what to loosen them to when it's public, plus server-side guards to add then.
GuardDemo (now)Live (production)
Idle auto-end (no speech)45 seckeep — 60–90 sec
Hard cap — video (Anam)2.5 min~8–10 min backstop
Hard cap — voice (ElevenLabs)3.5 min~8–10 min backstop
Re-open limit (per browser/day)5keep / raise
Worker-side per-IP/day capADD (real abuse guard)
Global $ budget guardyou opted outper-channel limit bars instead (top panel)
Unrestricted for my own testing: visit once with ?dev=<token> → stores localStorage['cz-dev']=1 and skips all caps on that browser, any network (not IP-based). Proposed token ?dev=sozou-ok. Idle auto-end is the #1 guard (forgotten tabs); keep it on always. Server-side guards are overkill for one colleague but essential once public.