Two organisations, one governed job, two records that agree.
A supplier’s agent and a buyer’s agent work the same order. Each side keeps its own directory and its own record. The badge narrows at the boundary, and both records show what crossed it.
The same door, on both sides of the boundary.
In market terms this is constrained delegation across organisations: the agent on the far side never holds more than the job it was handed.
Each side keeps its directory
Your people and agents stay in your directory. Theirs stay in theirs. Nobody gets an account in the other company.
The badge narrows at the boundary
The badge that crosses is what both sides allow for this job, and nothing more. A step outside it is refused at the door, on either side.
Two records that agree
Each side keeps its own record of the exchange. Both show the same badge, the same steps and the same refusals.
Three ways to connect agents across companies.
Most cross-company agent work today is a one-off integration per partner, or a shared hub one party controls.
| Bilateral integration | Central hub | Ares | |
|---|---|---|---|
| Each side keeps its own directory | Yes | No | Yes |
| Permission narrows per job at the boundary | Partial | Partial | Yes |
| Out-of-badge steps refused at the door | Partial | Partial | Yes |
| Each side keeps its own record | Partial | No | Yes |
| Both records show the same exchange | No | No | Yes |
| No single party can rewrite what happened | No | No | Yes |
| Adding a third partner | Another integration | Join the hub | Same door, new badge |
Categories, not products. Individual integrations and hubs vary; ask us for a comparison with the one you run.
What crosses the boundary
- The badge for this job: what the far-side agent may do, for whom, and until when.
- The request and the answer, inspected on the way out and on the way in.
- The fact of each decision: allowed, refused, redacted or sent to a human.
What never crosses
- Your directory. Group memberships and credentials stay with the organisation that issued them.
- Anything your filters keep out. A redaction leaves only a note of which rule fired.
- Standing access. When the job ends, the badge ends with it.
Where this fits
- Supply chain. A buyer’s agent asks a supplier’s agent for a quote. The supplier sees the parts it needs to price, not the buyer’s full bill of materials.
- Coalition and partner programs. Two allied organisations, two directories, one tasking. Only what the badge allows is released, and both sides keep the proof. See defence.
- Insurer and broker. The broker’s agent submits a risk. The insurer’s agent reads the submission, never the broker’s client book.
- Bank consortium. Member banks run checks against a shared question. Each bank answers from its own systems, and each keeps its own record of what it shared.
Supplier agent, buyer agent, one order.
The buyer’s agent asks for a quote. The supplier’s agent tries to read more than the job needs and is refused at the boundary. The quote still comes back, and both records are shown side by side.
Pick a prompt and press Run. Every action is checked against the badge before it happens.
open a session for this job
issue the badge: read open order · request quote · write order
read the open order
hand order line 3 to the supplier's quote agent
read the buyer's full bill of materials
price the order line
return the quote to the buyer
approve the quote above the threshold
write the order to the buyer's record
write the quote to the supplier's record
The record fills in as the run happens.
Real agents, real decisions. The records shown are a replay of this run's decisions on an isolated demo network.
What partners ask first.
Bring the partner you want to work with.
Tell us the job your agents need to do across the boundary. We will show you what crosses, what never does, and what both records hold.