# Multi-Agent System

> Source: https://netray.co/glossary/multi-agent-system
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Glossary

## Short answer

A multi-agent system uses several specialised AI agents, each with its own instructions and tools, coordinated by an orchestrator to complete a larger task. For example, separate agents for inventory, suppliers and finance feed one recommendation.

## Aliases

- multi-agent AI
- agent orchestration
- agent swarm

## Category

on-prem-ai

## Full Definition

A single agent with dozens of tools and a long prompt tends to pick the wrong tool and lose track of the goal. A multi-agent design splits the job. A planner or orchestrator breaks a request into sub-tasks, hands each to a specialist agent with a narrow toolset, and combines their outputs. A procurement agent sees supplier and purchase order tools, an inventory agent sees stock and planning tools, and a finance agent sees cost and payables tools.

Common patterns include orchestrator and workers, a pipeline where one agent's output feeds the next, and a reviewer agent that checks another agent's draft against rules before a human sees it. Each agent can use a different model: a small fast model for routine lookups and a larger model for planning.

The costs are real. More agents mean more model calls, more latency, harder debugging and more places for errors to compound. Many ERP tasks, such as answering a question over live data, work well with one agent and good tools. Multi-agent designs earn their place when tasks are long, cross functional boundaries, or need independent checking.

Governance gets harder as well. Every agent needs scoped permissions, every handoff should be logged, and writes should still pass through a human approval step. Agents that talk to each other can also pass along injected instructions, so treat inter-agent messages as untrusted input.

## Why It Matters

- Narrow toolsets improve tool-selection accuracy compared with one overloaded agent.
- A reviewer agent adds an automated check before humans spend time on a draft.
- Cross-functional ERP workflows, such as shortage to expedite to cost impact, map naturally onto specialists.
- Complexity and cost rise quickly, so it should be adopted only where one agent falls short.

## In Practice

A weekly shortage review runs three agents. The planning agent lists components short for jobs due within 10 days. The supplier agent checks open PO dates and past delivery performance for each short item. The cost agent estimates expedite charges versus line-down cost. The orchestrator merges the results into one ranked list of actions for the buyer, who approves each purchase change.

## Faq

### Do I need multiple agents for ERP automation?

**Answer:** Often not. Start with one agent and well-designed tools, and split into specialists only when tool confusion, prompt size or the need for independent review becomes a problem.

### Can different agents use different models?

**Answer:** Yes. Routine retrieval can use a small local model while planning or review uses a larger one, which controls cost and GPU load.

### How do I stop agents making things worse together?

**Answer:** Give each agent least-privilege tools, log every handoff, set step and cost limits, and keep human approval on writes.

### What is the main risk?

**Answer:** Compounding errors and injected instructions passing between agents. Treat agent outputs as untrusted input and validate before acting.

## Search terms

multi agent system, multi agent ai erp, agent orchestration, ai agent workflow manufacturing, orchestrator agent, agentic erp, ai agents supply chain, agent to agent

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json