Digital Library

Building Live Voice Agents (Heiko Hotz Sokratis Kartakis)(Z-Library)

Share E-Book

Building Live Voice Agents (Heiko Hotz Sokratis Kartakis)(Z-Library)

Author

Rating 3.5 AI initial rating

Log in to rate

Artificial Intelligence
Language English

Create AI agents that listen, respond aloud, handle interruptions, and use visual context as a conversation unfolds. This book takes you from agent fundamentals to architecting live, multimodal, multi-agent systems, focusing on the difficult leap from proof of concept to production.

Format EPUB
Size 13.7 MB

AI Guide

AI Reading Assistant

Whole-book reading guide from stratified index samples; jump to passages in the text

Full assistant
AI guide
【One-Line Pitch】 A production-minded field guide for engineers who can already get a voice agent to talk in a demo and now need it to survive real users, real latency, and real interruptions. Read it if you are building streaming, multimodal, tool-using agents and want architecture and operations, not model theory. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core thesis — demos are easy, live agents are hard — and states the book's scope: streaming audio, video sampling, interruptions, tool calls, and multi-agent routing, all under production constraints. It also sets expectations about what the book is *not* (no model training, no exhaustive framework survey). - **Early (~10%–35%)**: Lays the vocabulary and roadmap. Part I covers intelligent agents, collaborative AI, and multimodality beyond text (speech, vision, fusion, multimodal output), then previews the six-part structure from foundations through protocols to productionization. - **Middle (~35%–55%)**: Traces the historical arc from classic deliberative/reactive/hybrid agents and multi-agent systems to the GenAI stack — foundation models, prompting, private-knowledge gaps, and retrieval — showing how LLMs slot into older architectural blueprints rather than replacing them. - **Late (~55%–85%)**: Moves into interoperability and system assembly: A2A for agent-to-agent delegation, MCP for standardizing tool interaction, then a reference architecture that integrates live APIs, agent frameworks, specialists, and tool servers, plus async and long-running task handling. (Excerpts do not detail the individual implementation chapters.) - **Ending (~85%–100%)**: Productionization — AgentOps, live multimodal evaluation and testing, tool management at scale, agent registries and gateways, an eight-layer security and responsible-AI treatment, and CI/CD deployment toward an automated "agent factory." (Excerpts summarize these chapters at outline level only.) 【Key Takeaways】 - **The hard problem is the leap from demo to production, not the demo** (Opening): The book's organizing claim is that live voice and multimodal interaction change the engineering shape — timing, state, media handling, and tool contracts become bottlenecks — and most enterprise initiatives stall exactly there. - **Architecture should be inspectable by failure domain** (Early): The authors deliberately separate browser from backend, direct model calls from framework-managed execution, and agent-to-agent delegation from tool-server integration so a failure can be localized to media capture, transport, tool execution, serialization, or UI. - **Every design choice has a user-visible consequence** (Early): Streaming audio over WebSocket, keeping credentials server-side, exposing a specialist via A2A, or returning structured metadata via MCP each changes what users can interrupt, what the system can explain, what is testable, and what is replaceable. - **Modern agents inherit classic agent blueprints** (Middle): Deliberative, reactive, hybrid, and multi-agent designs from pre-LLM research supply the architecture; LLMs supply a new reasoning engine to drop into those time-tested structures. - **Foundation models are generalists that need private context** (Middle): Their broad but shallow knowledge creates the gap that retrieval and tooling fill — the book treats models as application components, not things you train. - **Protocols are boundaries, not features** (Late): A2A and MCP are presented as contracts that determine responsibility and replaceability; the conceptual chapters explain the protocol, the implementation chapters show how the boundary shapes code. - **Evaluation must become live and multimodal** (Ending): Traditional text benchmarks are reframed toward evaluating real-time, multimodal behavior, with background agents used for testing and guardrails. - **Productionization is a people-process-technology problem** (Ending): AgentOps extends DevOps/MLOps with registries, gateways, identity propagation, layered security, and CI/CD quality gates — the "agent factory" is an organizational capability, not a library. 【Reading Tips】 - Read Part I even if you know agents; the shared vocabulary (multimodality, fusion, agent ingredients) is reused throughout and skipping it makes later chapters harder. - If you are protocol-focused, Part IV (A2A, MCP) can stand alone; if you own product experience, jump to the UX chapter in Part V; if you operate systems, Part VI is your track. - Deep-read the reference architecture and the trade-off discussions; skim the historical agent survey if you already know deliberative vs. reactive paradigms. - Treat the companion code as illustration, not drop-in production code — the authors explicitly bound examples, and those boundaries are part of the lesson. - Expect the hardest material in latency, interruption handling, and identity propagation; budget extra time there. 【Coverage Limits】 These excerpts are dominated by front matter, the preface, and chapter outlines; individual implementation chapters, code detail, and worked examples are largely absent, so this guide maps the book's structure and stated arguments rather than its technical specifics.

Passage locations

Excerpt 1
rchased for educational, business, or sales promotional use. Online editions are also available for most titles ( https://oreilly.com ). For more information...
View in text
Excerpt 2
ramework comparison. The book uses specific frameworks (e.g., Google's Agent Development Kit [ADK], Gemini APIs) and protocols where they make the architectu...
View in text
Excerpt 3
erms, URLs, email addresses, filenames, and file extensions. Constant width Used for program listings, as well as within paragraphs to refer to program eleme...
View in text
Excerpt 4
classic agents , have to do with the modern world of GenAI. In fact, this history isn't just a prelude; it's the essential foundation we're still building on...
View in text

Recommended for You

Loading recommended books...
Failed to load, please try again later

Tip the Site

Scan the WeChat Pay or Alipay code to tip. No login required.

WeChat Pay
Alipay
← Back to List