Tragentics Docs

Networks & Routing

Private connections

Private connections link two entities through the Tragentics proxy. They support three connection types — agent-to-agent, agent-to-app, and agent-to-website — each designed for a different integration pattern.

Three connection types

Agent-to-Agent

A direct peer connection between two of your agents. The source agent calls the target agent through the proxy. This is the most common connection type — used for orchestrator-to-sub-agent communication, chained pipelines, and internal routing.

Agent-to-App

Connect an agent to an external application — Salesforce, Slack, GitHub, or any service with an API. The connection stores the app's endpoint URL and authentication configuration. Your agent calls the app through the proxy with credentials injected automatically.

Agent-to-Website

Connect an agent to a webhook endpoint or website URL. Designed for outbound notifications, webhook triggers, and HTTP callbacks. The proxy forwards the agent's request to the configured URL with optional authentication headers.

Creating a connection

Create private connections from the Privatetab on any agent's manage page.

1

Open the Private tab

Navigate to My Agents, click on an agent, then select the Private tab. Click the connection type you want — Agent-to-Agent, Agent-to-App, or Agent-to-Website.

2

Select source and target

Choose the source agent (the caller) and the target (the destination). For Agent-to-Agent, both are agents from your fleet. For Agent-to-App and Agent-to-Website, the target is a URL with optional authentication configuration.

3

Choose a network and group name

Select an existing network or create a new one. Enter a group name — this is required and organizes the connection within the network. Groups are how you cluster related connections together.

4

Click Connect

The connection is created immediately. A unique connection ID is generated — this is what the source agent uses in the proxy URL to call the target.

The connection ID

Every private connection receives a unique connection ID. The source agent uses this ID in the proxy URL to route calls to the target.

POST /api/proxy/{connectionId}
Authorization: Bearer tk_source_agent_api_key
Content-Type: application/json

{"message": "Hello from the source agent"}

The connection ID is displayed in the Private tab, in the Network Contents view on the Networks page, and in the Canvas detail panel. Copy it from any of these locations.

Viewing connections

Private connections are visible in multiple places:

  • Private tab — on the agent's manage page, shows all connections involving that agent
  • Network Contents — on the Networks page, shows all connections in the selected network grouped by private group
  • Canvas — visual topology view with solid edges and lock icons for private connections
Source Agent
Private Connection
Target Agent

Private connections appear as solid edges with a lock icon on the Canvas. The source agent sends requests; the target agent receives them.

Deleting connections

Delete a connection from the Private tab, the Network Contents view, or the Canvas detail panel. Deletion is immediate and permanent — the connection ID becomes invalid and any proxy calls using it will fail. The agents themselves are not affected and can be reconnected.

Deleting a connection invalidates its connection ID immediately. Any agent still calling that ID will receive an error. Make sure to update your calling agent's configuration before deleting.

Next

Connections are organized into groups. Learn about Private groups →