Tourbook — tour routing by

Tourbook — tour routing by taste, not population

Indie tours are routed by population: New York, Los Angeles, Chicago, the biggest rooms and the highest costs. The fans of a mid-size act often over-index in cities no booking agent would put first.

What I built • A planning agent that ranks 34 US metros with a Hidden Market Score: taste against population • A fan heat map, a route, and a With / Without Qloo toggle that shows what taste data changed • A dossier for each date: room, opener, sponsor, after-show spot and crowd brief, each citing its source • Ask Tourbook: one change in plain words, verified by the server before it applies • Room mode for venues, a tour poster, a phone layout, light and dark, English and French

Result • Tested live on Qloo data: one plan makes 30 to 31 Qloo calls across 5 endpoints, 0 rejected parameters • Ask Tourbook: 15 of 15 requests valid, 60 of 60 independent checks pass • Built for the Qloo Agentic Hackathon 2026; open source (MIT)

My role: Product design, UX/UI, agent design, front-end, back-end, demo film Stack: Node.js, Express, JavaScript, MapLibre GL, Qloo Insights API, Google Gemini, Server-Sent Events, Render Watch the demo: https://youtu.be/5O4NPcu1zE0 | Code: https://github.com/blanco1er/tourbook