# How Airbnb builds Trust for Guests and Hosts using AI Agents with LangGraph

## Executive summary

Pedro Rodriguez of Airbnb details the architectural patterns required to build and, critically, to establish trust in high-stakes AI agents. The core lesson is that while building the agents is straightforward, ensuring their reliability, explainability, and consistency—especially when wrong decisions impact real guests or hosts—requires complex systems like structured outputs, multi-layered verification, and robust state management using tools like LangGraph. The presentation outlines five key patterns for achieving enterprise-grade AI trust.

## Key takeaways

- Structured Outputs and Abstain Paths: Agents should use typed outputs (e.g., decision, reason, summary) rather than free text to ensure explainability. Crucially, agents must be allowed to 'abstain' when uncertain, routing the case to human review to prevent confident wrong answers.
- Subagents and Plain Rules Layer: Complex tasks should be decomposed into smaller, specialized subagents for easier testing and maintenance. This workflow should be fronted by a plain rules layer (non-AI logic) to handle obvious cases (e.g., missing data, policy mandates) immediately, reducing token usage and complexity.
- Handling Long-Running States with Interrupts: For cases that require days or weeks to resolve (common in trust/insurance), the agent workflow must save its state (using LangGraph interrupts) and separate the case data into an external database, allowing the process to resume without losing context.
- Mandating a Single Data Access Layer (MCP): All agent interactions with internal systems must pass through a dedicated layer (MCP). This layer serves as the single point of evidence, enforcing rigorous logging and access controls, making every decision fully traceable.
- Multi-Layered Verification (The Checker): Trust requires verification beyond standard evaluation (evals). Implement multiple checks: LLM judges (checking policy adherence), code checks (tool calls, malformed responses), and a separate 'checker' model (from a different model family) to ensure two identical inputs yield identical outputs.

## Technical details

- LangGraph Architecture: LangGraph was chosen for its superior handling of complex state transitions, external system connections (edges), and the ability to support 'stop and replay' functionality necessary for long-running, asynchronous cases.
- Data Flow Control (MCP): The Model Control Plane (MCP) acts as the sole gateway between AI agents and core data systems, ensuring that all agent decisions are logged and auditable.
- State Management: For long-running processes, the case state must be stored externally in a database, rather than solely within the graph's memory, to allow for querying across multiple runs and systems.

## Practical implications

- Architects must treat AI agents not as black boxes, but as systems requiring explicit, auditable control planes (like the MCP).
- Reliability testing must move beyond simple average performance metrics (evals) to include live, comparative verification (e.g., running two identical inputs through the system to check for consistency).
- State management for AI workflows must account for asynchronous, multi-day processing times, necessitating external, persistent storage mechanisms.
- Decomposition of agent tasks into small, rule-governed subagents increases maintainability and failure isolation.

## Topics

AI Agents, LangGraph, Trust and Safety, Structured Outputs, MLOps, System Architecture, LangGraph interrupts docs, Introduction to LangGraph on LangChain Academy

Source: https://www.youtube.com/watch?v=NUgaWmws0XQ
