AI-powered triage for Hong Kong Typhoon claims.
Five agents. $100 of hardware. 24/7 coverage.
Peak season: May–October. T8+ signals trigger claims surges lasting 24–72 hours.
Human teams simply cannot scale fast enough.
Sentiment-based routing in <3 seconds. Each agent has a distinct personality.
Seamless handoff to human queue when needed. GL8 compliant throughout.
Live AI agents responding to typhoon claims
6 typhoon scenarios fire in real-time
Real-time SLA, tNPS, agent utilisation
🎬 Demo flow: /simulator → Fire "Mrs. Chan — Flooded Flat" → Watch /triage update live → Show /metrics
Mixed mode: Grace runs on hardware. Swift, Kara, Phoenix, Triage stay in simulation.
The dashboard looks identical. Validate first — then add boards one by one.
picoclaw gateway — an HTTP server with agent-specific personality baked into the system prompt.
Board ordered from AliExpress. SD card flashed. Firmware ready.
Board arrives. Run setup script. Deploy PicoClaw. First agent live.
5 boards deployed. Full hardware agent cluster. Pre-typhoon season.
Single env var switches between modes:
AGENT_MODE=simulation|hardware
Dashboard is identical. Only the agent calls change — from local functions to HTTP calls to board IPs.
| Item | Cost | Notes |
|---|---|---|
| 5 × LicheeRV Nano boards | $100 | One-time hardware cost |
| Claude API (claude-sonnet) | ~$5/day | During active typhoon surge |
| Power (5 boards × 2W) | <$1/mo | Running 24/7 |
| AI total (surge day) | ~$5 | Handles 1,000+ interactions |
| Human agent (surge day) | $400–800 | 8 agents × $50–100/day |
| AI containment target | >50% | Reduces human load by half |
Every agent identifies as AI on first contact. Human option always visible.
API keys via environment variables only. .gitignore enforced. Never in repo.
X-Frame-Options, X-XSS-Protection, Content-Type-Options, Referrer-Policy.
ESLint security plugin running on every commit. TypeScript strict mode.
In-memory store (no DB). No raw query construction anywhere.
All API routes validate inputs. Hard overrides prevent prompt injection escalation.
Operator endpoints need auth before production. Prototype deliberately open.
Add API rate limiting before production to prevent abuse.
Today: running on a laptop, demonstrating the full system.
March: running on $100 of hardware, one board per agent.
May: live for HK typhoon season, before peak hits.