ASCN API — How to Build a Product Based on an Agent

A single agent handles most small business tasks just fine. But as the business grows, more tasks appear, different departments emerge — and it makes sense to split into multiple specialized agents.

Think of it as the difference between one "jack-of-all-trades" employee and a team of specialists.

When you need multiple agents

One agent is enough if:

• All tasks fall under one area (e.g., operations only)
• Fewer than 5–7 active tasks
• One person manages the agent
• Tasks don't conflict in tone or context

Multiple agents are needed if:

• Different departments with different tasks and different owners
• You need different "personalities" — the marketing agent speaks lively and creatively, the finance agent speaks precisely and formally
• Different levels of data access (a marketer shouldn't see financial analytics)
• More than 10 active tasks — a single agent starts "mixing up contexts"

Real-world example: a digital agency with three agents

Context: An agency in Moscow, 15 people, three departments: marketing, sales, and operations.

Agent 1: Marketing