Hub / Topics / Agent-to-agent support

Agent-to-Agent Support with TSANet

Support platforms now ship AI agents that can call outside tools and, increasingly, other companies' agents. Two open protocols carry that traffic. Neither says who an outside agent belongs to, what agreement covers the exchange, or which partner agent handles a given product, and those are the questions TSANet already answers for people. This page sets out what the protocols and the platforms support today, where a neutral member organization fits, the direction TSANet is considering, and what you can do with an agent and Connect right now. Nothing on the agent-to-agent side is built, and every claim says how it was checked.

Topic Agents working partner cases across companies Grounded in The A2A and MCP specifications, vendor documentation, the Connect API specification Status Direction under consideration; nothing built Updated 2026-11-17

Read This Before You Rely on Anything Below

This page describes a direction, not a product. The protocol and platform facts were read from the sources in the Verified against table on the dates shown there. The TSANet pieces are proposals: none is approved, scheduled or built, and none has been tried against a member's agent platform. What works today is the Connect REST API, which any agent can already call.

Connect REST APILive. Callable by any agent with a member's credentials. SHIPPED
MCP server for ConnectNone exists. Under consideration. PROPOSED
A2A endpoint and support extensionNone exists. Under consideration. PROPOSED
Member agent directoryNone exists. Under consideration. PROPOSED
Terms for agentsNone exist. A change to the Code of Conduct and an opt-in addendum are under consideration. PROPOSED
PRIMARY read in the specification or the vendor's own documentation SECONDARY read in a third-party write-up or a search summary of the vendor's page NEEDS PROBE not verified, and known not to be

The gap

What the Protocols Leave Open

The protocols make it technically cheap for one company's agent to reach another's. They solve the connection. They do not solve four things that two support organizations have to settle before their agents can work a mutual customer's problem:

QuestionWhat the protocols sayWhat TSANet does today, for people
Who is this agent, and which company answers for it?A2A lets an agent sign its own card. Verifying that the signer is who it claims to be is left to whoever runs a registry. No cross-company agent identity standard has been ratified.Vets members before they can open or receive a case.
What agreement covers what the two agents exchange?Out of scope for both protocols.One Code of Conduct, with an addendum for each relationship type, in place of a contract between every pair of members.
Which partner agent handles this product, and what does it need to start?A2A describes curated registries but does not define one.The partner directory, and each partner's process form with its required fields.
What happened on the case, and who is accountable?Each side keeps its own task history.One case record that both members see, with a respond-by time.
Trust across companies: where TSANet sits Who is this agent? member vetting, a directory What covers it? the Code of Conduct Who handles this? partner directory, forms Who answers for it? one case record Open protocols: one vendor-neutral foundation A2A: agent to agent tasks, signed agent cards, extensions MCP: agent to tool tools and resources Vendor platforms: each governs agents inside one company's boundary Agentforce ServiceNow Copilot Studio Zendesk Fin In-house
The bottom two layers exist and are converging. The top layer is the part no protocol or platform fills, and it is the part TSANet already operates for human support teams.

As read

The Two Protocols

MCPA2A
What it connectsAn agent to a tool or data source.An agent to another agent, which takes on a task.
GovernanceThe Agentic AI Foundation, under the Linux Foundation. PRIMARYThe same foundation. PRIMARY
Version readSpecification 2026-07-28. PRIMARYSpecification 1.0.0. PRIMARY
What matters hereA server must accept only tokens issued for itself and must not pass them on to another service. Sessions are gone: each request stands alone. Machine-to-machine sign-in is an optional extension, not part of the core.An agent describes itself in a card that can be signed. Registries of cards are described but deliberately not standardized. A formal extension mechanism lets a group add rules for one use case without changing the protocol.
What it does not coverShared memory or context between agents.Shared memory, and trust between organizations.
Extensions cannot change the protocol's core objects. An A2A extension may add structured data and metadata. It may not add fields to core objects or new task states. Any support-specific design therefore has to carry Connect's own case status beside the A2A task state, not in place of it. PRIMARY

Comparison

What Members' Platforms Support

Every platform below can reach an outside MCP server. Fewer speak A2A. The column that decides whether a hosted server is usable is the third one: how the platform is able to sign in to it.

PlatformMCPA2ASign-in it offers to an outside MCP serverEvidence
Salesforce AgentforceClient and serverInbound and outbound; an administrator registers each outside agentNone, or OAuth client credentialsPRIMARY
ServiceNowClient and server; its client speaks MCP 2025-06-18Client and receiver, on A2A v0.3 rather than 1.0; no streaming, parallel tasks or artifacts yetNone, an API key, or OAuthPRIMARY vendor community and documentation
Microsoft Copilot StudioClient; server in previewCalling other agents is generally available. Being called is in preview, in early-release environments only, for a signed-in user of the agent's own tenant. Whether another company's agent can call in is NEEDS PROBENone, an API key, or OAuth with a signed-in userPRIMARY see Agentic usage
Microsoft Dynamics 365 Customer ServiceServer, open to non-Microsoft clientsNone foundNot applicable: it is a serverPRIMARY
ZendeskClient; no server confirmedNone foundNot readSECONDARY
FinClient and serverNone foundA fixed token, or OAuth through one connection shared by the whole workspace; no per-user sign-inPRIMARY for sign-in; SECONDARY for the rest

Three things follow from the table.

Nothing here has been probed. No TSANet component has been registered in any of these platforms, and no primary source was found describing a cross-vendor support escalation running agent to agent in production. Treat the table as a reading list, not a compatibility matrix.

Direction

Three Pieces Under Consideration, None Built

The direction is to extend what TSANet already does for people to agents, on top of the open protocols, and not to invent a protocol or operate agents. Members' agents stay the members' own, on whatever platform and model they choose.

Proposed

An MCP Server for Connect

A hosted server a member registers once in its agent platform. Its tools find a partner, read the partner's process form, open a case, respond, add notes and close, under the member's own Connect credentials. It holds no cases; Connect stays the record.

Proposed

An A2A Support Extension

A published extension that says how a collaboration case travels as an A2A task: the fields a partner's form requires, how Connect's case status maps to task states, and how either side asks for a person to take over.

Proposed

A Member Agent Directory

A curated registry of members' support agents, in which TSANet attests that each agent belongs to a member in good standing. A2A leaves registries to implementers; the attestation is the part a membership body can supply.

Design rules the direction holds to

How terms for agents might be adopted

Members accept a Code of Conduct, and each relationship type is defined by an addendum to it. Neither mentions automated agents. The approach under consideration has two parts, because they would bind different members.

A short change to the Code of ConductAn opt-in agent addendum
Would coverTwo confidentiality points. What an agent retains is not the unaided memory of a person, which the Code excuses. Training or tuning a model on a partner's case content is not a permitted use of it.Operating terms: the member answers for its agent, a partner is told when it is dealing with an agent, either side can require a person, how long partner content is kept, and listing in the directory.
Would bindEvery member, because these points protect the member whose content it is.Only members that accept it, before their agents take part.
Adopted byThe Board, under the Bylaws, with notice to members before it takes effect.The Board, then accepted by each member that wants it.
Neither has been drafted, reviewed by counsel or put to the Board. This describes an approach, not a decision. A member whose agent calls the REST API today acts under the agreements it has already accepted. PROPOSED
Submitter's agent any platform or model TSANet exchange (proposed) checks who the agent belongs to keeps the Connect case as the record: status, respond-by time, notes Receiver's agent if the partner has one Receiver, no agent connector or web app task 1 task 2 as today
One case, two tasks. Agents do not talk to each other directly in this shape: each talks to TSANet, and the Connect case joins the two sides. That keeps one record and one respond-by time, and it means the submitter does not need to know whether the partner has an agent.

Mapping

A Collaboration Case as an A2A Task

Connect's case statuses line up with A2A's task states closely enough that a case can be carried as a task. The statuses below are from the Connect API specification. The mapping is a first pass, and which transitions Connect allows between them has not been checked on Beta.

Connect case statusA2A task stateNote
OPENSubmitted or workingWaiting for the receiving member to respond.
INFORMATIONInput requiredThe receiver has asked the submitter for more.
ACCEPTEDWorkingAn engineer is engaged on the receiving side.
REJECTEDRejectedFinal on both sides.
CLOSEDCompletedFinal on both sides. Connect has no reopen.

A2A's states are coarser than Connect's, so the Connect status would travel in the task's metadata and remain the authority. Notes map to task messages. NEEDS PROBE

Now

What You Can Do Today

None of the proposed pieces is needed to put an agent to work on partner cases. The REST API is the same for an agent as for a connector.

Rules worth adopting now, whatever is built later

Unknowns

Open Questions

QuestionWhat it decides
Which sign-in mode reaches a working call from each platform against a hosted Connect MCP serverWhether one server serves every platform, and where it has to run
Whether platform agents can send A2A structured data and activate a custom extension, or only textWhether a support extension is usable from those platforms or only from in-house agents
Which transitions Connect allows between case statusesThe lifecycle mapping above
Whether the two confidentiality points clarify the Code of Conduct or change it, and how an opt-in agent addendum is adoptedThe terms agents work under, and everything beyond a tool server. A question for counsel and the Board, not engineering
Whether members want this yetThe order of the three pieces, and whether to build them at all
If you are building an agent that works partner cases, say so. The most useful input is which platform your agent runs on and how it is able to sign in to an outside service. Send feedback to membership@tsanet.org.

Verified against

Sources, with the Dates That Were Read

Read onSourceUsed for
2026-11-10A2A specification 1.0.0, agent discovery and extensionsTask states, signed agent cards, registries left unstandardized, what an extension may and may not change
2026-11-10MCP specification 2026-07-28: authorization and key changesToken audience rule, no token forwarding, removal of sessions, machine-to-machine sign-in as an extension
2026-11-10Agentic AI FoundationBoth protocols hosted by one foundation
2026-11-10Salesforce: Agentforce interoperability guide, register an external MCP serverA2A inbound and outbound, MCP registration and its sign-in types
2026-11-10ServiceNow: enable MCP and A2A (FAQ), Action FabricMCP client and server, A2A roles, sign-in types; re-read 2026-11-17 for the A2A and MCP versions (page last updated 2026-09-04)
2026-11-10Microsoft: What's new in Copilot Studio, MCP and A2A channels (preview) (read 2026-11-17), Dynamics 365 Customer Service MCP server, agents across a multitenant organizationA2A general availability, inbound MCP and A2A in preview and their sign-in, the MCP server and its clients, single-tenant agent identities
2026-11-10Fin: add MCP connectorsSign-in types for a custom MCP server; re-read 2026-11-17 for the shared OAuth connection
2026-11-10Third-party write-ups and search summariesZendesk's MCP client; Fin's MCP server and client roles. Marked secondary where used
2026-11-10The Connect API specification (private repository)Case statuses
2026-11-11TSANet legal documents: the Code of Conduct, the relationship addenda and the BylawsWhat members agree to today, and how the Code is changed
not probedAny TSANet component registered in any agent platform; inbound A2A on Copilot Studio from another company's tenant; Connect's status transitions; structured data and extensions from platform agentsEach is marked where it appears