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.

Agentforce Network

A registry, not a private mesh of HTTP.

Network is how agents discover and invoke each other with declared skills. Discovery is not permission.

Get the written assessment Agent Broker

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

The difference

A private mesh, or a network?

Private mesh

Registry and A2A

Agents call each other over hand-written HTTP: Each agent declares its skills and scopes
Nobody can list which agent may call which: A register someone on your team can audit
Each pair has its own key: Identity travels with every call
A failed hop is found by a customer: Every hop is traced

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.

Public reference for Agentforce Network. A shared space holds common skills. A private space holds the desk that cannot share memory or identity. The gateway still fronts both.

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"]

Who this is for

Two estates where agents already call each other.

Typical first registers. One agent alone does not need a network yet.

Example
Platform lead, Riyadh bank
Today: The service agent calls the KYC agent through a wrapper only one engineer understands.
After: Both sit in a registry with declared skills, so someone can audit who may call whom.
Banking and finance
Example
Operations director, Dubai hotel apartments group
Today: The booking agent and the housekeeping agent share one memory, guest details included.
After: Housekeeping runs in a private space, so desk-scoped memory stays with that desk.
Hotel apartments

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

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.

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. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.