Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: the control plane does not run the router
Tomas Tormo418cebf56f66
diff --git a/site/content/docs/getting-started/_index.md b/site/content/docs/getting-started/_index.mdindex 161c6fcc..13062f13 100644--- a/site/content/docs/getting-started/_index.md+++ b/site/content/docs/getting-started/_index.md@@ -4,9 +4,12 @@ linkTitle: "Getting started"weight: 1----Every Agent Mesh has a **control plane** (which enrolls members, distributes-policy, and runs the router) and the **members** (`agentmesh-node` or native SDK-programs) that connect to it.+Every Agent Mesh has a **control plane**, one or more **routers** and the+**members** (`agentmesh-node` or native SDK programs). The control plane+enrolls members and distributes policy. The routers keep the directory of+members and their services. A router relays traffic between two members+that cannot connect directly. The members enroll with the control plane and+connect to the routers.To connect an agent or machine to a mesh, you need **a running control planeand its URL** (`https://...`).