Agentforce Network
A registry, not a private mesh of HTTP.
The first week is in the org, reading what already exists. Network is how agents discover and invoke each other with declared skills. Discovery is not permission. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
Jobs
What the network is for.
Runtime
Shared space when it is safe. Isolated when it is not.
One runtime for common tools. A private space when the desk, the tenant, or the policy cannot share memory.
01
Caller
A person, a schedule, or another agent. Identity is already on the hop.
02
Broker
Routes to a declared skill. Does not invent a new agent for every exception.
03
Shared or private
Share the tools that are safe to share. Isolate the memory and the tenant that cannot.
04
Gateway
MCP and model calls still go through Flex Gateway. The space does not skip the front door.
Mermaid source
flowchart TD
A["Caller: Slack, Salesforce, schedule"] --> B["Broker"]
B --> C["Shared space: common skills"]
B --> D["Private space: desk-scoped memory"]
C --> E["Flex Gateway"]
D --> E
E --> F["MCP and systems of record"]Questions
What we actually say.
- Do we need a network for one Agentforce agent?
- Not on day one. It becomes the job the moment a second runtime appears, or when two agents must call the same MCP tools with different rights.
- Is a private HTTP wrapper between agents a network?
- No. A2A and a registry are. A shim you cannot register is a finding.
Next
What to read next.
The brief · one email
Name the agents that already call each other.
We will mark which hops have no registry, and which should not exist.
