---
title: "Multi-agent architectures · real production systems + reference diagrams · Agent Fieldbook"
url: https://agentfieldbook.org/design/architectures/
description: "Real production multi-agent systems partners have built, with the internal agent breakdown drawn from public sources. Each system is diagrammed by role (orchestrator, sub-agents, tools, gates, human) and cites its engineering blog or press announcement."
section: "Design · Architectures"
source: Agent Fieldbook — generated from the published page
---

# Real systems + reference architectures

**Financial services · hub-spoke · LangGraph · HITL · AI research / consumer · swarm-dispatch · Anthropic internal (Claude Agent SDK precursor) · Amazon Bedrock Agents (multi-agent collaboration) · Fintech / consumer · recursive · OpenAI Assistants API (custom orchestration layer) · Financial data / media · Custom (Bloomberg internal) · Consumer / mobility · Custom (Uber Michelangelo + LangChain components) · Consumer / travel · sequential · Custom (Airbnb internal AI platform) · AI research · swarm · Custom (DeepMind) · AutoGen · Enterprise CRM · Agentforce (Atlas Reasoning Engine) · SQL databases · Internal APIs · Vector store (unstructured docs) · Python code execution · Proprietary financial models · Web search · Web browsing · Internal memory / scratchpad · Bedrock Knowledge Bases · Bedrock Data Automation · Bedrock code interpreter · Market data APIs · Order-management APIs · Payments APIs · Refund system · Knowledge base retrieval · Bloomberg data feeds · BloombergGPT · Vector search over research · Terminal function APIs · Internal KB · Past-ticket vector store · Policy engine · Case-history API · LLM (summarisation prompt) · Code execution sandbox · Verifier / benchmark harness · Gemini model · Chromium browser · Python execution sandbox · Local filesystem · Data Cloud · Knowledge base · Flow · Apex · Prompt Builder**

Real production multi-agent systems partners have built: with the internal agent breakdown drawn from public sources. Every row cites its engineering-blog or press announcement.

## Production case studies · 10 · scan the index, then read the diagram below

| System | Org | Industry | Topology | Framework | Composition |  | src |
| --- | --- | --- | --- | --- | --- | --- | --- |
| **Ask David** | J.P. Morgan | Financial services | hub-spoke | LangGraph | 6 agents· 5 tools | HITL | [↗](https://blog.langchain.com/customers-jpmorganchase/) |
| **Multi-Agent Research System** | Anthropic | AI research / consumer | swarm-dispatch | Anthropic internal (Claude Agent SDK precursor) | 3 agents· 3 tools |  | [↗](https://www.anthropic.com/engineering/multi-agent-research-system) |
| **Investment-Research Multi-Agent Assistant** | Amazon Web Services (reference architecture) | Financial services | hub-spoke | Amazon Bedrock Agents (multi-agent collaboration) | 4 agents· 4 tools |  | [↗](https://aws.amazon.com/blogs/machine-learning/part-3-building-an-ai-powered-assistant-for-investment-research-with-multi-agent-collaboration-in-amazon-bedrock-and-amazon-bedrock-data-automation/) |
| **Klarna OpenAI Support Assistant** | Klarna | Fintech / consumer | recursive | OpenAI Assistants API (custom orchestration layer) | 2 agents· 4 tools | HITL | [↗](https://www.klarna.com/international/press/klarna-ai-assistant-handles-two-thirds-of-customer-service-chats-in-its-first-month/) |
| **Bloomberg AI Assistant** | Bloomberg | Financial data / media | hub-spoke | Custom (Bloomberg internal) | 4 agents· 4 tools |  | [↗](https://arxiv.org/abs/2303.17564) |
| **Genie· Uber Support Copilot** | Uber | Consumer / mobility | recursive | Custom (Uber Michelangelo + LangChain components) | 2 agents· 3 tools | HITL | [↗](https://www.uber.com/blog/genie-ubers-gen-ai-on-call-copilot/) |
| **Airbnb Support Summarisation** | Airbnb | Consumer / travel | sequential | Custom (Airbnb internal AI platform) | 3 agents· 2 tools | HITL | [↗](https://medium.com/airbnb-engineering/automation-platform-v2-improving-conversational-ai-at-airbnb-d86c9386e0cb) |
| **AlphaEvolve** | Google DeepMind | AI research | swarm | Custom (DeepMind) | 3 agents· 3 tools |  | [↗](https://deepmind.google/discover/blog/alphaevolve-a-gemini-powered-coding-agent-for-designing-advanced-algorithms/) |
| **Magentic-One** | Microsoft Research | AI research / consumer | hub-spoke | AutoGen | 5 agents· 3 tools |  | [↗](https://www.microsoft.com/en-us/research/articles/magentic-one-a-generalist-multi-agent-system-for-solving-complex-tasks/) |
| **Agentforce Service Agent** | Salesforce | Enterprise CRM | recursive | Agentforce (Atlas Reasoning Engine) | 4 agents· 5 tools | HITL | [↗](https://www.salesforce.com/agentforce/what-is-agentforce/) |

## Detailed architectures

Investment-research assistant for portfolio managers, analysts and traders: answers natural-language queries by querying structured databases, unstructured research documents and proprietary financial models.

## Internal agents · 6

## Tools + data

- [↗ T2 · confirmed](https://blog.langchain.com/customers-jpmorganchase/)

Powers Claude's Research feature, parallel sub-agent search across the web with source citation, used inside claude.ai for the depth-research mode.

## Internal agents · 3

- [↗ T1 · confirmed](https://www.anthropic.com/engineering/multi-agent-research-system)

AWS-published reference architecture for a multi-agent investment-research assistant on Bedrock: the template many banks and asset managers now base their internal builds on.

## Internal agents · 4

- [↗ T1 · confirmed](https://aws.amazon.com/blogs/machine-learning/part-3-building-an-ai-powered-assistant-for-investment-research-with-multi-agent-collaboration-in-amazon-bedrock-and-amazon-bedrock-data-automation/)

Customer-service AI assistant that handled ~2.3M conversations in its first month, two-thirds of Klarna's chat volume, doing the work of ~700 full-time agents.

## Internal agents · 2

- [↗ T1 · confirmed](https://www.klarna.com/international/press/klarna-ai-assistant-handles-two-thirds-of-customer-service-chats-in-its-first-month/)

In-terminal assistant for Bloomberg Professional users: natural-language queries over 40+ years of proprietary financial data, news and research.

- [↗ T1 · likely](https://arxiv.org/abs/2303.17564)

Internal assistant used by Uber's customer-support agents: surfaces answers from internal knowledge base and past resolutions to shorten handle time.

- [↗ T1 · confirmed](https://www.uber.com/blog/genie-ubers-gen-ai-on-call-copilot/)

Summarises long customer-support case histories for the agent before they engage: reduces handle time and improves first-response quality.

- [↗ T1 · confirmed](https://medium.com/airbnb-engineering/automation-platform-v2-improving-conversational-ai-at-airbnb-d86c9386e0cb)

Evolutionary coding-agent system that discovers novel algorithms: has produced verified improvements to matrix-multiplication and data-centre scheduling algorithms.

- [↗ T1 · confirmed](https://deepmind.google/discover/blog/alphaevolve-a-gemini-powered-coding-agent-for-designing-advanced-algorithms/)

Open-source generalist multi-agent system for complex tasks: browse, code, file navigation. Reference architecture behind Copilot Actions.

## Internal agents · 5

- [↗ T1 · confirmed](https://www.microsoft.com/en-us/research/articles/magentic-one-a-generalist-multi-agent-system-for-solving-complex-tasks/)

Reference internal deployment on the Salesforce sales + support stack: customer-facing autonomous service agent grounded in Data Cloud + Knowledge.

- [↗ T1 · confirmed](https://www.salesforce.com/agentforce/what-is-agentforce/)

## Field notes

How real teams wire orchestrators, sub-agents, tools and human gates

These architectures show a clear build pattern: one supervising unit, a small number of narrow workers, and a gate before anything irreversible. Businesses are converging on it independently because it is the arrangement that stays debuggable as the fleet grows.

- [Brandon Chaplin](https://www.linkedin.com/in/brandon-chaplin-digital-marketing-strategist)

## Common questions

### What does a real multi-agent system look like?

Almost always the same arrangement: one orchestrator holding the plan, a few narrow sub-agents doing the work, a fixed set of tools they are allowed to call, and a human approval step before anything irreversible. Teams arrive at it independently because it stays debuggable as the system grows.

### Which companies run multi-agent systems in production?

Ones with public write-ups include Anthropic's research system, Klarna's support assistant, Uber's support copilot, Bloomberg's assistant, Airbnb's ticket summarisation, DeepMind's AlphaEvolve and Salesforce Agentforce. Most are support, research or internal tooling rather than anything customer-facing and fully autonomous.

### What is human in the loop?

A point where the system stops and waits for a person to approve, correct or take over. It is normally placed just before anything irreversible: sending money, emailing a customer, deleting records. Everything before the gate can run unattended.

### What is an orchestration framework?

The software that coordinates the agents: it runs the steps, passes state between them and handles retries. LangGraph, AutoGen, Amazon Bedrock Agents and the OpenAI Agents SDK are common choices, and several large teams have written their own instead.

### Do multi-agent systems cost more to run?

Considerably. Every agent adds its own model calls, and an orchestrator that reasons about each step pays for that reasoning too. Anthropic measured its multi-agent research system using around 15 times the tokens of an ordinary chat [(Anthropic)](https://www.anthropic.com/engineering/multi-agent-research-system).

### When should I split one agent into several?

When sub-tasks can genuinely run at the same time, or when one job needs a different tool set or a different model. Splitting for tidiness alone adds handoffs where context gets lost. A single agent with good tools is cheaper and easier to debug for most work.

## Next in the learning path

- [Topologies The shapes these systems instantiate](https://agentfieldbook.org/design/topologies/)

- [Building blocks The parts inside each system](https://agentfieldbook.org/design/building_blocks/)

- [Orchestration The frameworks that coordinate them](https://agentfieldbook.org/design/orchestration/)

- [Runtime How these systems persist state](https://agentfieldbook.org/design/runtime/)

- [Governance The oversight gates in these flows](https://agentfieldbook.org/security/governance/)
