Softlander Book a call
Agent-to-agent interoperability

Agent interoperability assessment

Decide whether agents can exchange work without losing meaning or control

Agents built by different teams must cooperate in one workflow. The decision is how to decide whether agents can exchange work without losing meaning or control. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to integration architects and platform product owners. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.

Book a 30 minute readiness callBrowse this capability group

The interaction contracts relationship

  1. Starting evidenceInteraction diagrams

    Establish the basis for discovery contract.

  2. Decision boundaryTask handoff

    Align ownership and progress states.

  3. Decision artefactInteroperability assessment

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested peers require their own compatibility evidence.

Decision

Frame the decision around discovery contract

Questions and the evidence they need

Criterion / evidenceDiscovery contract
Inspect interaction diagrams for the relevant constraint or observation.
Criterion / evidenceTask handoff
Inspect message contracts for the relevant constraint or observation.
Criterion / evidenceResult interpretation
Inspect identity mappings for the relevant constraint or observation.
Read each criterion against the available evidence before deciding that additional work is needed.

The decision is how to decide whether agents can exchange work without losing meaning or control. This is relevant to integration architects and platform product owners when agents built by different teams must cooperate in one workflow. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.

The specific failure hypothesis is that messages are accepted syntactically while participants disagree about completion or authority. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.

Mechanism

Interoperability includes authority and shared task meaning

Relationships within interaction contracts

Source or conditionDiscovery contract
Identify eligible peers and supported interaction scope.
Crossing or choiceTask handoff
Align ownership and progress states.
Consequence or decisionResult interpretation
Reconcile completion and error meaning.
Compare authority and state at the receiving boundary. Each relationship needs evidence in the actual scope.

What this specialty examines

Interoperability assessment should trace a business task across participating systems. Compare discovery, identity, task acceptance, progress, completion and failure semantics. Transport success is only one observation; participants also need compatible expectations about what the exchange means.

The review should trace a representative task across discovery, delegation, progress, result and error paths. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.

The tradeoff to make explicit

For this decision, flexible integrations accommodate differences while implicit semantics make failures hard to detect. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.

Preparation

Connect the working inputs to the boundary being examined

Evidence packet for discovery contract

Illustrative working format

BasisInteraction diagrams
Match this description to the deployed or proposed boundary being examined.
ContextMessage contracts
Check its relationship to the relevant workflow and expose missing context.
ObservationIdentity mappings
Match this description to the deployed or proposed boundary being examined.
DependencyTask-state definitions
Identify provenance and the specific decision this material can inform.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with interaction diagrams, message contracts, identity mappings and task-state definitions. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.

The scope also needs the integration owner, agreed expectations for a representative interaction case, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which messages are accepted syntactically while participants disagree about completion or authority from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.

How the work proceeds

Carry discovery contract through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsInteraction diagrams

    Agree the task meaning at the sending boundary.

  2. Examine the relationshipTask handoff

    Apply the scoped check to result interpretation.

  3. Retain the findingInteroperability assessment

    Record the evidence, open dependencies, and the owner’s next decision.

Proposed sequence; resolve interpretation or access gaps before relying on the next step.

Fix the interaction contract and versions

Assemble interaction diagrams, message contracts, identity mappings and task-state definitions with integration architects and platform product owners. Identify the participating implementations, interface revisions, authority assumptions and intended business result. Prepare messages and task-state examples from both sides, including an interrupted exchange and a disputed or incomplete outcome. The preparation output is a paired contract fixture showing what each participant expects and which differences would prevent the workflow from completing correctly.

Run and compare both sides of the exchange

Use a representative handoff and inspect both sides’ state. Include cancellation, delayed updates and incomplete results. Record where adapters supply assumptions that the protocol itself does not establish, and assign ownership for resolving those differences.

Choose the contract or integration change

Summarise the comparison in an interoperability assessment with contract gaps and proposed compatibility cases. Classify each mismatch as interface validation, business meaning, identity, task state or operating behaviour. Decide whether to change a participant, add an explicit adapter rule, narrow supported combinations or defer the connection. Validate the affected pair again and preserve limitations that translation cannot resolve, especially around cancellation, authority and partial completion.

Indicative artefact

Make the interoperability assessment usable by its owner

Interoperability assessment

Illustrative working format

Annotated fieldInteroperability assessment
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldContract gaps
Name the missing evidence, responsible owner, and condition for revisiting the decision.
Annotated fieldCompatibility cases
Name the unresolved condition, next action, and accountable owner.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is an interoperability assessment with contract gaps and proposed compatibility cases. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.

Illustrative scenario

Examine result interpretation through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationDiscovery contract

    Two agents exchange valid messages but disagree about whether work is complete.

  2. Question to examineTask handoff

    Compare each participant's task owner and terminal-state definition.

  3. Conditional next actionResult interpretation

    Resolve the semantic gap before treating accepted messages as interoperability.

Fictional example. No executed test, customer engagement, or measured outcome is implied.

Consider a fictional situation: one agent reports complete after drafting a response while its partner expects a committed system update. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For draft versus committed work, define the accepted terminal state explicitly. A receiver may return a draft while the initiator retains responsibility for submission. The integration should represent that division instead of labelling both stages complete.

Scope and next action

Keep the conclusion within named implementations and revisions

Confirm fit before the next commitment

Included boundaryDiscovery contract
This review is limited to named implementations and revisions.
PrerequisiteInteraction diagrams
The relevant owner must confirm access and the intended operating conditions.
Claim limitInteroperability assessment
Untested peers require their own compatibility evidence.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Compatibility is assessed for named implementations, versions, features and workflows. It does not establish universal conformance, vendor endorsement or interoperability with untested peers. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which agents built by different teams must cooperate in one workflow; confirm which missing observation would change the owner’s next action.

Ways to engage

Related engagement scopes

AI Agent Protocol Interoperability Lab

Find where connected agents disagree. Exercise message contracts, identity propagation and failure recovery across your selected integrations.

Read about this offer

Continue exploring

Related insights and resources

Evaluation & assurance6 MIN READ

How to design a joint AI evaluation lab

A joint lab should be a governed way to create decision evidence across organisations, with shared methods but explicit ownership of systems, data and conclusions.

Agent security6 MIN READ

Agent protocols are creating a new control surface

Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.

Agent security6 MIN READ

A practical security review for an MCP server

Review an MCP server as a privileged protocol adapter: verify tool semantics, OAuth boundaries, token audience, downstream delegation, input handling, isolation, logging and consent.

A little more clarity

Questions to consider.

Start with the questions that shape a better decision.

Does successful message exchange establish interoperability?

No. Participants must also agree on identity, authority, state and business meaning. A schema-valid exchange can still leave the workflow incomplete or incorrectly interpreted.

Which contracts define cross-agent task meaning?

Start with interaction diagrams, message contracts, identity mappings and task-state definitions. Record their revision, owner and relationship to the intended workflow. Missing context should be identified before interpreting outcomes; a sanitised fixture is useful only when its relevant differences from the operating case are understood.

How should completion and error states be compared?

Trace a representative task across discovery, delegation, progress, result and error paths. Compare both participants' accepted inputs, task states and results under a named interface revision. Include interrupted or delayed interactions. Parser acceptance should not be treated as agreement about business meaning, authority or completion.

What belongs in an interoperability assessment?

The proposed output is an interoperability assessment with contract gaps and proposed compatibility cases. Include the selected conditions, supporting observations, unresolved differences and next decision. A reviewer should be able to follow each important conclusion back to its evidence and understand the limits without depending on an undocumented explanation from the author.

When does successful transport conceal a workflow mismatch?

Transport success conceals a mismatch when peers disagree about authority, task meaning, progress or final state. Inspect both participants' records rather than treating an accepted message as completed business work.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from integration architects and platform product owners may already be sufficient. In that case, capture the decision, unresolved limitations and the change that would require another review. Additional assessment should address a real gap.

What would make the findings inconclusive?

Missing interaction diagrams, message contracts, identity mappings and task-state definitions can prevent a reliable interpretation, depending on the case. Record the specific missing observation and its implication. The owner can supply evidence, narrow the claim or defer the dependent decision; an incomplete case should not silently be counted as a pass.

Start with the decision you need to make.

Tell us about the agent workflow you want reviewed, and where you need greater clarity. Scope and availability are confirmed together.

Book a 30 minute readiness call Get the agent release checklist

Connected disciplines

MCP architecture and security

Design an MCP integration around explicit resource and authority boundaries. The review connects client and server configurations, tool inventories, identity flows and data paths to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

Agent2Agent protocol evaluation

Evaluate a chosen Agent2Agent implementation against workflow expectations. The review connects selected specification revision, implementation documentation, task states and authentication settings to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

Agent protocol compatibility testing

Verify compatibility between concrete agent protocol implementations. The review connects version matrices, supported features, message examples and failure responses to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.