Agents & Scenarios
Pre-built agents, industry scenarios, and tool catalog.
Industry Scenarios
A scenario defines: which agents, how they connect, and what the entry point is.
# Pattern for every scenario
start_agent: EntryPoint # Who answers first
agents: [...] # Who participates
handoffs: [...] # How they connect
agent_defaults: {...} # Shared variables| Scenario | Entry Agent | Pattern | Agents |
|---|---|---|---|
| Banking | BankingConcierge | Hub & spoke | 5 (Cards, Fraud, Investment, KB, Auth) |
| Insurance | AuthAgent | Security gate | 6 (Policy, Claims, FNOL, Subro, Compliance) |
| Healthcare | Concierge | Triage-first | Extensible via MCP |
Banking Scenario
Hub-and-spoke pattern. The BankingConcierge routes to specialists based on intent.
| Handoff | Type | When |
|---|---|---|
| Concierge → Cards | discrete | Balance, cards, spending questions |
| Concierge → Fraud | announced | Suspicious activity reported |
| Concierge → Investment | discrete | Retirement, portfolio questions |
| Any → Auth | announced | Identity verification needed |
Insurance Scenario
Security-gate pattern. AuthAgent verifies identity before routing to specialists.
| Handoff | Type | When |
|---|---|---|
| Auth → Policy | announced | After identity verified, policy questions |
| Auth → FNOL | announced | After identity verified, new claim |
| Claims → Subro | discrete | B2B subrogation processing |
| Policy → Compliance | announced | Regulatory or compliance flag |
Healthcare Scenario
HIPAA-compliant triage flow. Extensible through the MCP healthcare server.
MCP Integration: The healthcare scenario uses a separate MCP server (apps/healthcare-async-mcp/) for FHIR-compliant patient data access, appointment scheduling, and clinical decision support.
Cross-Domain Agents
Available in all scenarios.
| Agent | Role | Key tools |
|---|---|---|
| Concierge | Default entry point. Routes to specialists based on intent. | All handoff tools |
| AuthAgent | Identity verification via MFA (SSN, phone, employee ID). | verify_identity, send_mfa_code |
| GeneralKBAgent | Knowledge base Q&A. RAG retrieval for general questions. | rag_retrieval |
| ComplianceDesk | AML, FATCA, sanctions screening. Regulatory compliance checks. | compliance_check |
Banking Agents
| Agent | Role | Key tools |
|---|---|---|
| BankingConcierge | Primary banking entry point. Service-first routing. | All banking handoff tools |
| CardRecommendation | Credit card recommendations, balance checks, spending analysis. | check_balance, recommend_card |
| InvestmentAdvisor | Retirement accounts, portfolio allocation, risk assessment. | get_portfolio, risk_assessment |
| FraudAgent | Post-authentication fraud investigation. Suspicious transaction review. | flag_transaction, freeze_account |
Insurance Agents
| Agent | Role | Key tools |
|---|---|---|
| PolicyAdvisor | Policy details, coverage explanations, renewal info. | lookup_policy, explain_coverage |
| ClaimsSpecialist | Existing claim status, documentation requests, updates. | claim_status, request_docs |
| FNOLAgent | First Notice of Loss. New claim intake. | create_claim, capture_details |
| SubroAgent | Subrogation (B2B). Third-party recovery processing. | initiate_subro |
Tool Catalog
All tools are registered with @register_tool in toolstore/ and shared across agents.
| Category | Tool | Description |
|---|---|---|
| Auth | verify_identity | SSN/phone/employee ID verification |
send_mfa_code | Send MFA code via email/SMS | |
validate_mfa_code | Validate MFA code entry | |
| Banking | check_balance | Account balance lookup |
recommend_card | Credit card recommendation engine | |
| Fraud | flag_transaction | Flag suspicious transaction |
freeze_account | Temporary account freeze | |
| Insurance | lookup_policy | Policy details retrieval |
create_claim | New claim creation (FNOL) | |
| Transfer | call_transfer | SIP transfer to human agent |
handoff_* | Agent-to-agent handoff tools (auto-generated) | |
| Knowledge | rag_retrieval | RAG-based document retrieval |
MCP Integration
Tools can also be exposed via Model Context Protocol servers, enabling external tool providers.
| MCP Server | Purpose | Location |
|---|---|---|
| Healthcare MCP | FHIR patient data, appointments, clinical support | apps/healthcare-async-mcp/ |
| Card API MCP | Card decline code lookup and search | apps/cardapi/ |
MCP tools are discovered at startup and merged into the tool registry alongside built-in tools. Agents reference them the same way — no code difference between built-in and MCP tools.