Core Concepts

Networks & groups

Networks are containers that organize your agent topology. Inside each network, Tragentics stores direct connections, grouped connections, app and website lanes, broadcasts, pools, and schedules.

What is a network

A network is a named container that holds connections and groups. Think of it as a project folder — it keeps related agent connections organized and separate from unrelated ones.

When you register your first agent and create a connection, Tragentics creates a Default Network automatically. You can rename it, create additional networks, and move entities between them.

Example: separating environments

A team might create three networks: Production (live agents handling real traffic), Staging (testing new configurations), and Development (experimental connections). Each network has its own topology, visible independently on the Canvas.

Networks are scoped to your current account or org context. Other users do not browse directly into your network graph. Cross-user collaboration happens through the invite system, not by sharing networks.

What lives inside a network

A network can contain both grouped and ungrouped topology records. The main routing entities are:

Private connections

Direct agent-to-agent links. One agent calls another through the proxy. Connections can live ungrouped or inside private groups for logical separation. See Private connections.

Broadcast groups

One orchestrator agent sends a single request to multiple member agents simultaneously. All members receive the same payload, and results are aggregated. See Broadcast groups.

Agent pools

One orchestrator routes each request to a single member based on a strategy — round-robin, failover, or random. The pool provides load balancing and redundancy. See Agent pools.

Schedules

Automated cron-based triggers that call target agents on a recurring schedule — hourly, daily, weekly, or monthly. See Scheduled calls.

App and website connections

Networks also hold app-connected and website-connected lanes. These are tracked alongside agent-to-agent topology and appear in network-level counts and deletion behavior.

Private groups

Within a network, private connections are organized into private groups. A group is simply a named cluster of connections — it helps you keep related connections together.

For example, you might have a network called "Production" with three private groups:

Intake Pipeline — connections between your intake agent and processing agents
Analysis Cluster — connections between your analysis agents
Output Handlers — connections to delivery/notification agents

Groups are a visual and organizational tool. They don't affect the private routing mechanics — a direct proxy call between two agents works the same regardless of which private group the connection is in.

The hierarchy

Your Account

├── Network: Production

├── Private Group: "Intake Pipeline"

├── Agent A → Agent B

└── Agent A → Agent C

├── Broadcast: "Alert Fan-out"

└── Orchestrator → [Agent D, Agent E, Agent F]

├── Pool: "Processing Pool"

└── Orchestrator → [Agent G (pos 1), Agent H (pos 2)]

└── Schedule: "Hourly Check"

└── Cron → Agent B, Agent C (daily at 09:00)

└── Network: Staging

└── Private Group: "Test Connections"

└── Agent A-staging → Agent B-staging

Where to manage networks

Networks appear in three places:

Networks page — account-wide view of all networks, connections, memberships, invites, and audit log
Canvas — visual topology editor where you see agents as nodes and connections as edges within a selected network
Agent manage page — the Private, Broadcast, Pools, and Schedule tabs let you create and manage entities within networks for a specific agent

Deleting a network

Deleting a network cascades to the topology anchored to that network: private connections, private groups, broadcast groups, pools, schedules, and the app or website connection rows assigned to that network. The agent profiles themselves are not deleted.

Network deletion is permanent and cannot be undone. A confirmation dialog will ask you to verify before proceeding.

Networks organize the structure. The proxy handles the communication. Learn how the proxy works →