Across organisations

When the work crosses to a supplier, the rules follow.

A buyer’s agent and a supplier’s agent work the same job. Each company keeps its own directory and its own record. The permission narrows at the boundary, and both records show what crossed.

The work

A buyer asks for a quote. A supplier answers it.

The buyer’s agent asks the supplier’s agent to price the parts on one request. The supplier sees the parts it needs to price, not the buyer’s full bill of materials. The quote comes back. Each company keeps its own record of the exchange, and both records show the same steps.

  • Each side keeps its own directory
  • The permission narrows again at the boundary
  • Both records show what crossed, and what did not
How it works

The same rules on both sides of the boundary.

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 permission narrows at the boundary

The permission that crosses is what both sides allow for this job, and nothing more. A step outside it is refused, on either side.

Two records that agree

Each side keeps its own record of the exchange. Both show the same permission, the same steps and the same refusals.

What crosses the boundary

  • The permission for this job: what the far-side agent may do, for whom, and until when.
  • The request and the answer. Each is checked before it leaves and read at the door on the far side.
  • The fact of each decision: allowed, refused, redacted or sent to a person.

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 permission ends with it.

Where this fits

  • Supply chain. A buyer’s agent asks a supplier’s agent for a quote, a delivery date or a certificate. The supplier answers from its own systems.
  • Primes and subcontractors. A prime hands a task to a subcontractor’s agent. Only what the permission allows is released, and both sides keep the record. See defence and government.
Run it yourself

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 the step 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 permission before it happens.

1Conciergeagent
buyer · workflow builder

open a session for this job

waiting
2Conciergeagent
buyer · workflow builder

issue the credential: read open order · request quote · write order

waiting
3Nooragent
buyer · planning

read the open order

waiting
4Nooragent
buyer · planning

narrow the permission for the supplier: order line 3 · quote it

waiting
5Solagent
supplier · quotes

read the buyer's full bill of materials

waiting
6Vikagent
supplier · pricing

price the order line

waiting
7Solagent
supplier · quotes

return the quote to the buyer

waiting
8Purchasing leadhuman
buyer · purchasing

approve the quote above the threshold

waiting
9Docsmcp
buyer · document store

write the order to the buyer's record

waiting
10ERPmcp
supplier · order system

write the quote to the supplier's record

waiting
The 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.

Compare

Three ways to connect agents across companies.

A one-off integration is good for one fixed partner. A shared hub works when every party trusts the one that runs it. Both stop where the record has to belong to each side.

  • Each side keeps its own directory

    Bilateral integration
    Yes
    Central hub
    No
    Ares
    Yes
  • Permission narrows per job at the boundary

    Bilateral integration
    Partial
    Central hub
    Partial
    Ares
    Yes
  • Steps outside the permission are refused

    Bilateral integration
    Partial
    Central hub
    Partial
    Ares
    Yes
  • Each side keeps its own record

    Bilateral integration
    Partial
    Central hub
    No
    Ares
    Yes
  • Both records show the same exchange

    Bilateral integration
    No
    Central hub
    No
    Ares
    Yes
  • Adding a third partner

    Bilateral integration
    Another integration
    Central hub
    Join the hub
    Ares
    A new permission

Categories, not products. Individual integrations and hubs vary. Ask us for a comparison with the one you run.

Questions

What partners ask first.

What it does not do

  • It does not work with a partner that has no Ares in front of its agents.
  • It does not decide what to share. Each side sets its own permission.
  • The records show what crossed, not whether the deal was right.

Bring the supplier job you want to run.

Tell us the work your agents need to do across the boundary. We will show you what crosses, what never does, and what both records hold.

A senior member of the team replies within two business days.