AI Agent Protocol Interoperability Lab
Find where connected agents disagree. Exercise message contracts, identity propagation and failure recovery across your selected integrations.
Agree what a handoff means before relying on it
- Capability contract
- State the task the receiving agent may accept.
- Message version
- Compare schema meaning and compatibility assumptions.
- Delegated identity
- Carry the authorised principal across the boundary.
- Failure response
- Assign responsibility for timeout and partial completion.
Decision and fit
Agree what a handoff means before relying on it
Compare the engagement with the decision you face
- A question worth resolving
- Agree what a handoff means before relying on it.
- An accountable participant
- Integration leads joining agent runtimes, tool servers or partner systems whose message and authorisation contracts may differ.
- Inspectable source material
- The relevant owners can make workflow evidence and agreed inputs available for examination.
- A scope mismatch
- The task is procurement advice without a defined integration contract.
The engagement
Find where connected agents disagree. Exercise message contracts, identity propagation and failure recovery across your selected integrations. A controlled integration lab against a named matrix of protocol versions, implementations and failure cases.
The decision at stake
Two agents can exchange messages without agreeing on meaning, permissions or responsibility when work fails.
Suitable situations
- Integration leads joining agent runtimes, tool servers or partner systems whose message and authorisation contracts may differ.
Less suitable situations
- The task is procurement advice without a defined integration contract.
Engagement boundary
Agree the work and its boundaries together
The engagement boundary
- Capability contract
- Agree message contracts and expected behaviour at each integration boundary.
- Message version
- The inputs, authorised access and client participants are confirmed before scheduling.
- Integration owner
- Retains organisational decisions and risk acceptance.
- Additional implementation
- Untested implementations and future protocol revisions are outside the result. Production integration, third-party fixes and ongoing compatibility monitoring require a further scope.
What the work covers
- Agree message contracts and expected behaviour at each integration boundary.
- Exercise identity propagation, incompatible messages and partial failures.
- Document compatibility gaps and the conditions required for reliable handover.
Scope boundaries
- Formal certification, legal conclusions and guarantees of safe or compliant behaviour.
- Implementation or ongoing operation beyond the agreed scope.
- Untested implementations and future protocol revisions are outside the result. Production integration, third-party fixes and ongoing compatibility monitoring require a further scope.
Working sequence
How the work moves from question to handover
What each stage should leave your team with
- Freeze the compatibility matrix
An explicit version and implementation matrix.
- Write contract cases
Message, identity and error-handling contracts.
- Exercise disagreements
Observed compatibility under disagreement and failure.
- Hand over repeatable checks
Repeatable tests and unresolved integration dependencies.
How the work proceeds
- Freeze the compatibility matrix. Choose the implementations, protocol versions, authentication paths and operations that must interoperate.
- Write contract cases. Specify messages, capability negotiation, error responses and identity propagation at each boundary.
- Exercise disagreements. Run malformed-message, timeout, partial-failure and version-mismatch cases without real business side effects.
- Hand over repeatable checks. Record supported conditions and failures, supply contract tests and assign integration or vendor follow-up questions.
Worked situation
Follow one situation through to a bounded next decision
Illustrative working situation
Illustrative scenario
- Starting condition
A receiving agent accepts a message with an unknown field.
- Question to examine
Inspect contract interpretation and failure handling.
- Possible next action
Resolve the incompatible contract before extending the handoff.
Decision artefacts
Leave a record the next owner can use
Compatibility finding
Illustrative working format
- Subject and version
- Identify the workflow, configuration or proposal examined.
- Capability contract
- Record the relevant requirement and supporting material.
- Delegated identity
- State the observation, supporting evidence and remaining uncertainty.
- Integration owner
- Record the next decision, follow-up and unresolved question.
What the work can produce
- Protocol compatibility matrix
- Contract and failure test suite
- Integration findings and remediation options
Working together
Your team and our team need a clear working agreement
Who contributes and who decides
- Client sponsor
- Confirms the decision, priorities and people needed to resolve it.
- Client technical or process owner
- Provides the agreed evidence, access and review of findings or deliverables.
- Softlander delivery lead
- Coordinates the agreed activities, review points, handover and open actions.
- Authorised decision-maker
- Accepts deliverables against the agreed criteria and separately decides operational or business action.
What the work depends on
- Provide implementation owners on each side, interface specifications, supported versions, test credentials through an approved channel and a representative sandbox. Owners agree which compatibility behaviours are mandatory.
Engagement availability
The start date, named delivery roles, review points and fee basis are agreed after confirming the inputs and scope. Duration depends on evidence access, system complexity and the time your decision-makers need to review the work.
Engagement and handover
Agree the delivery model and what completion means
A clear agreement from scope to ownership
- Scoped work
- Agree message contracts and expected behaviour at each integration boundary.
- Indicative handover
- Protocol compatibility matrix; Contract and failure test suite
- Review and acceptance
- Review the agreed deliverables and record any open items, owners and conditions.
- Ongoing work
- Assign maintenance and operational ownership; agree additional scope and coverage explicitly.
A controlled integration lab against a named matrix of protocol versions, implementations and failure cases.
The compatibility matrix records exactly which combinations were exercised, the expected contract and observed result. Contract tests and reproduction instructions are handed to the integration owners with unresolved version dependencies.
Untested implementations and future protocol revisions are outside the result. Production integration, third-party fixes and ongoing compatibility monitoring require a further scope.