One orchestrator above every provider's agents
A global consumer-goods enterprise coordinated the agent systems of multiple managed-services providers under one neutral x101 orchestrator, tasking agents x101 did not ship over agent-to-agent protocol to determine root cause, drive resolution and produce the postmortem. Each provider had arrived with agent systems of its own. Delivered with a Big Four consulting partner, this proof of concept placed x101 above all of them, with the customer's own team designing agents and no vendor dependency.
Proof of concept · Consumer Goods · Europe
Last updated: 23 September 2026
The challenge
Every managed-services provider brought its own tooling and, increasingly, its own AI agents. Each was competent inside its own scope and blind outside it, so when an incident crossed provider boundaries, which real incidents usually do, root-cause analysis became a relay race between vendors with the customer holding the baton and the outage.
Provider agent islands
Each provider ran its own agents and tools, and none of them could see, or task, the others.
Cross-boundary incidents ping-ponged
Analysis across providers meant serial handoffs, with queues, lost context and finger-pointing.
No central accountability
No single layer owned the question of what actually caused this, and who fixes it.
Manual service-management choreography
Tickets, updates and closures were driven by hand across every provider boundary.
The customer locked out of automation
New automation meant a vendor change request, not work the customer's own team could do.
Postmortems assembled afterwards
Reconstructing what happened relied on memory and fragmented logs from several parties.
What x101 does
x101 was deployed as the neutral orchestration layer above the entire estate. It did not replace any provider's agents, it coordinated them: receiving the incident or the typed question, deciding which provider agents to engage, correlating what came back into a root cause, driving resolution, and writing the postmortem from the evidence gathered along the way.
One layer above the estate
x101 sits above every provider's agent system, holding the cross-estate picture that no single provider has.
Incident or question, either starts it
An incoming incident, or an engineer's question typed into chat, starts an orchestrated investigation across providers.
Agents tasked agent to agent
The orchestrator tasks and queries each provider's agents over the open agent-to-agent protocol, in parallel, and correlates their answers.
One determined root cause
Findings converge into a single root cause, and resolution is driven through the responsible provider's agents under governance.
Agents the customer built
The customer's own team designed its agents in Agent Studio, connected to their services through native connectors.
The postmortem writes itself
The full investigation and action trail becomes the postmortem, generated automatically rather than reconstructed by hand.
Governance held across every boundary. Each engagement of a provider agent, each service-management action and each resolution step ran through audited, reversible records, so a multi-vendor estate gained a single accountable trail for the first time.
The outcome
The proof of concept validated the pattern that matters most in multi-vendor operations: an orchestrator that makes other vendors' agents work together, while the customer's own team extends the system without waiting on anyone.
- A2A
Agents coordinated
Provider agents tasked in parallel over an open standard.
- One
Accountable trail
A single governed record across a multi-vendor estate.
- Self-built
Customer agents
Extended by the customer's own team, not by change request.
- Auto
Postmortems
Generated from the investigation rather than reconstructed.
| Dimension | Before | After · with x101 |
|---|---|---|
| Cross-provider analysis | Serial vendor handoffs, context lost at each hop | One orchestrated investigation, provider agents engaged in parallel |
| Accountability | No single owner of cause and fix | One governed layer holding the full evidence and action trail |
| Service management | Manual choreography across boundaries | Actions executed via native connector under governed records |
| Extending automation | Change requests to vendors | Agents built by the customer's own team, self-service |
| Access | Console-hopping and status calls | A typed question as the front door to an orchestrated investigation |
| Postmortems | Reconstructed from fragments, days later | Generated automatically from the investigation itself |
The estate already had plenty of agents. What it lacked was anyone above them. Proving that one orchestrator can task every provider's agents, determine the root cause and hand back a finished postmortem changed the conversation from which vendor's AI to who conducts them all.
Solution summary · x101 multi-provider orchestration proof of concept
The parts of x101 this uses
Nothing here was built for one customer. Each capability below is standard platform behaviour, applied to this problem.
Agentic Orchestration
Provider agents tasked and queried in parallel, their answers correlated into one root cause.
Explore Agentic OrchestrationFrom Answer to Action
Resolution and service-management actions carried through to done, under governance.
Explore From Answer to ActionBuild Your Own Agent
The customer's own team built and shipped agents without vendor dependency.
Explore Build Your Own AgentAI Explainability
The investigation trail is the evidence, and the postmortem is generated from it.
Explore AI ExplainabilityGoverned by Design
Every cross-boundary engagement audited and reversible.
Explore Governed by DesignNo Vendor Lock-in
An open agent-to-agent standard, so coordination is not proprietary.
Explore No Vendor Lock-in
About this case study. This was a proof-of-concept engagement: the scope was capability validation, not production operation. Customer and partner identities are withheld at their request, and the customer is referred to as a global consumer-goods enterprise.
Conduct every agent in your estate.
Agent-to-agent orchestration above your providers' agents, self-service agent building for your own team, and governed actions throughout.