Can we skip the gateway and call the model from the agent?

You can. You will not be able to prove who spent the tokens or which policy applied. We will not sign that as production.

Is Flex Gateway the same as Agent Fabric?

No. Flex Gateway is the edge. Agent Fabric is the control plane that inventories agents, MCP, and policies. You usually want both.

MuleSoft Flex Gateway

Every tool call gets a front door.

Flex Gateway is where identity, policy, and traces live. Agents do not get a shared key.

Get the written assessment Trusted identity

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

Jobs

What the gateway is for.

Identity

The user authenticates once. Every hop exchanges.

01
User authenticates
The identity provider issues the first token. The channel is Slack, a portal, or Salesforce.
02
Gateway exchanges
OAuth on-behalf-of credential injection. The next audience is narrower than the last.
03
Broker and agents
The broker routes. Downstream agents and MCP servers see a user, not a shared service account.
04
Trace
Which identity, which policy, which tool. That is observability, not a log dump.

Trusted agent identity: the user signs in. Each Flex Gateway hop exchanges for a narrower token scoped to the next audience. The agent does not run as a god-mode connected app unless you choose that, and we will say when that is a demo.

Mermaid source

flowchart LR
  U[User] --> C[Channel]
  C --> G1[Flex Gateway]
  G1 --> B[Broker]
  B --> G2[Flex Gateway]
  G2 --> A[Agent]
  G2 --> M[MCP]
  U -. authenticates .-> I[Identity provider]
  I -. OBO token .-> G1
  I -. OBO token .-> G2

MCP

Catalog, entitle, then serve.

The gateway is the front door for tools. Listing a server is not permission.

First
Catalog
Exchange versions the MCP servers agents may call.
Then
Entitle each caller
Business groups and contracts decide which tools that caller may use.
On every call
Policy on the hop
Client identity, access control, payload filter, spike control, logging. In that order.
After
Bill and audit
Token and tool usage tagged per caller, on the same trail as the traces.

AI Gateway

Model calls belong on the same door as tools.

Routing, budgets, and guardrails in one place. Not three SDK configurations and a hope.

01
Route by job
High-stakes judgement to a frontier model, classification and transforms to a fast one. Written down, not decided per engineer.
02
Meter per caller
Token accounting per business group, so a runaway loop is a throttle instead of an invoice.
03
Guardrails at the edge
Denied topics, PII detection, and response checks on the hop rather than inside each prompt.
04
Keep the choice reversible
A model swap should be a gateway change. If it is a rewrite, the routing was in the wrong place.

Model routing through the gateway. One entry point in front of frontier reasoning, fast high-volume models, open models inside your own perimeter, and dedicated forecasting models.

Mermaid source

flowchart TD
  A["Agents and applications"] --> G["AI Gateway: identity, policy, budget, audit"]
  G --> F["Frontier reasoning"]
  G --> H["High-volume extraction"]
  G --> L["Open models in your perimeter"]
  G --> T["Time-series forecasting"]

Who this is for

Two desks that put a door in front of the tools.

Typical gateway work. The agent stops holding its own keys.

Example
Security architect, Doha bank
Today: Agents call MCP tools with one shared key that never changes.
After: Each call carries a user-scoped token, and the tool list is entitled per caller.
Banking and finance
Example
Head of IT, Dubai property developer
Today: Three teams call three model APIs, each with its own budget and its own logs.
After: Model calls go through the same door as tools, with routing and budgets in one place.
For CTOs

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

Questions

What we actually say.

Can we skip the gateway and call the model from the agent?: You can. You will not be able to prove who spent the tokens or which policy applied. We will not sign that as production.
Is Flex Gateway the same as Agent Fabric?: No. Flex Gateway is the edge. Agent Fabric is the control plane that inventories agents, MCP, and policies. You usually want both.

The brief · one email

Show us what the agent can call today.

We will mark the hops with no identity, and the ones that 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.