Speaking twice at Dreamforce · Sept 15-17 →

Agent Broker

Not every hop is a model call.

The first week is in the org, reading what already exists. The broker picks a path. Deterministic when the work is known. A model when it is not. Traces on both. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

Observability

Three modes

Automation. Guided. Agentic.

We will not put a model on a hop that a router already owns.

  1. 01

    Automation

    Known path · No model · Idempotent

  2. 02

    Guided

    A rule · A person · A deterministic router

  3. 03

    Agentic

    A model call · A capability card · A policy at the gateway

  4. 04

    Observe

    Trace the hop · Identity on the trail · Cost on the same trail

Public reference for Agent Broker. Automation is a known path. Guided keeps a person or a rule in the loop. Agentic is a model call with a card and a policy. Observe sits across all three.
Mermaid source
flowchart TD
  A["Request"] --> B["Broker"]
  B --> C["Automation: known path"]
  B --> D["Guided: rule or human"]
  B --> E["Agentic: model with a card"]
  C --> F["Observe: traces"]
  D --> F
  E --> F

Lifecycle

Design. Publish. Deploy. Observe.

Questions

What we actually say.

Can the broker skip the gateway?
You can. You will not be able to prove who called what. We will not sign that as production.
What if the broker flags a memory fetch as an attack?
Tighten the cards and the policy. Memory is not prompt injection. If the platform cannot tell, that is a finding.
Can the broker route to a non-Salesforce agent?
Yes. A code agent is a peer with declared skills, reached over A2A through the gateway. The broker decides the hop; it does not care which runtime answers.

The brief · one email

Name the hops that are still a model.

We will mark which ones a router should own.