← All experiments
LiveStarted July 13, 2026Updated July 13, 2026
Can a voice agent host an entire website — answering questions, navigating you to any page, and even driving an interactive network graph?
Site-Wide Voice Guide
- ElevenLabs Conversational AI
- Next.js 16
- RAG (e5-mistral-7b)
- Supabase
Relevant services: AI & Digital Teammates
Hypothesis
Websites make visitors do the work: read, scan, click, guess where things live. A voice agent that knows the whole site could flip that — you say what you're curious about, and the site both answers and takes you there. If it can also operate interactive elements (like our ecosystem graph), the interface becomes a conversation.
What we built
A voice agent that lives in the bottom-right corner of every page on thrivbe.com — the same mic you'll find in the Thrivbe AI room, now site-wide.
Under the hood:
- Client tools, not just chat. The ElevenLabs agent has three tools the browser executes:
navigateToPage(routes you to any of ~70 pages),getCurrentPage, andselectEcosystemNode— which opens the ecosystem graph and highlights the organisation, country, or challenge you asked about, connections and all. - A self-updating site index. Every navigable page (services, projects, posts, all lab entries) is composed from the same registries that drive the sitemap, exposed at
/api/site-index. New page → next build → the agent's map is current. - RAG knowledge base generated from the site itself. A sync script pulls the live site index, all labs entries, and 600+ ecosystem organisations from Supabase, and rebuilds the agent's knowledge base — so the agent's answers and its navigation stay in lockstep with what's deployed.
Ask it "what does Thrivbe actually offer?" and it walks you to Services while summarising. Ask about Dark Matter Labs and it opens the ecosystem graph with the node selected.
Learnings
- The pattern that works is embarrassingly small: a site map in the prompt, one navigation tool, and an instruction to always navigate rather than wait to be asked. The agent's willingness to act is a prompt property, not a technical one.
- Every voice surface that shares an agent must register the same client tools — an agent with a
navigateToPagetool talking to a page without one fails mid-sentence. - Interactive components need a tiny public API for agents: one custom event + one URL param made a 2,000-line force-graph voice-drivable without touching its internals.
Log
- 2026-07-13 — First version live: global widget on every page, navigation across the full site index, ecosystem node selection, RAG knowledge base synced from the deployed site.
