Skip to main content

A2A Connection Guide

Last updated 11/05/2026

A2A connects Agents across different platforms. You can let an external platform call an AE Agent, or connect a remote Agent in AE so that the current Agent can delegate tasks to it and organize the results.

Overview and prerequisites​

Connection directionUse casesSetup entry point
External platforms call an AE AgentUse AE Agent capabilities on other platforms that support A2A.Get the Agent Card URL from the Agent page in AE, then connect through an external Agent session that can make calls or through an A2A configuration page.
AE calls a remote AgentLet the current Agent delegate specialized tasks to a remote Agent.Add an “A2A Remote Agent” on the MCP page, then associate it with the target AE Agent.

An Agent Card is a file that describes an Agent’s name, capabilities, protocol, and service URL. Enter the complete Agent Card URL when connecting, and confirm that the caller can access both that URL and the service URL declared in the Card.

The current connection requires a client or remote service compatible with A2A 1.0 JSON-RPC. To call an AE Agent, prepare a valid TE access token with permission to access that Agent and enable the target Agent. To connect a remote Agent from another platform, prepare the Bearer Token provided by that remote service.

Connect an AE Agent to an external platform​

  1. Go to the Agent page. To call the default Agent, click A2A 1.0 supported · View connection guide at the top of the page. To call a specific Agent, open its details and find External access (A2A).
  2. Click Copy URL to get the corresponding Agent’s Card URL. The default Agent and specific Agents use different URLs, so copy the URL displayed for the Agent you actually want to call.
  3. In an external Agent session that can execute HTTP requests and make calls using the A2A 1.0 protocol, send the Card URL and the task. You can also use the platform’s A2A connection configuration page. Both Card retrieval and subsequent task requests must include the following headers.
Authorization: Bearer <TE_ACCESS_TOKEN>
A2A-Version: 1.0

Replace <TE_ACCESS_TOKEN> with a valid TE access token. Obtain the token through the existing authentication method; the A2A connection window does not generate tokens. Copying the Card URL alone does not complete authentication, and browser cookies cannot replace the headers above.

To initiate a call through a session, send the following instruction together with the complete Card URL you just copied:

Please read this Agent Card and use the configured TE access credentials to call the Agent using A2A 1.0. Complete this task: correct the spelling in “The campaign will strat this Friday. You are welcome to join.”

The external Agent must actually read the Card and send protocol requests. A regular chat window receiving a link and text does not mean that an A2A connection has been established. If the platform has no tools for executing requests, use the A2A connection method it supports.

For your first use, verify a simple text task. If the response indicates that the task is running, continue querying its status. If the task requests additional input, reply within the original task.

In AE’s connection window, click View Card content to view the protocol, input and output types, and full JSON, and to copy the JSON. This preview uses your current signed-in identity. If the external platform uses different credentials, rely on the Card actually retrieved with those credentials.

External calls use the permissions of the user who owns the token and can access only Agents that are visible to that user and enabled. The connection URL must also be accessible from the external platform’s network.

Connect an A2A Remote Agent through MCP​

  1. Go to the MCP page and click + MCP.
  2. Select Personal MCP from the options provided on the page.
  3. Under Choose a connection, select A2A Remote Agent and enter the following settings.
Configuration ItemInstructions
Service Name (required)Enter an easily recognizable name, such as copy_editor. The name must start with an English letter and can contain only English letters, numbers, underscores, and hyphens.
Agent Card URL (required)Enter the remote Agent’s complete A2A 1.0 Card URL. To connect another AE Agent, use the URL copied from its connection window. Enter a Card URL here, rather than a regular MCP service URL.
Bearer Token (required)Enter a token with permission to access the remote Agent. Enter only the token itself, without the Bearer prefix. To connect an AE Agent, use a valid TE access token.
More settings (optional)Add a display name and description as needed to help users recognize the remote Agent’s purpose.
Allow private network or HTTP access to this address (optional)Off by default. Enable this only when access to a private network or HTTP URL is required. It allows only the host and port in the current URL. HTTP sends credentials and data in plain text, so HTTPS is recommended.
Remote execution model (optional)After entering the URL and token, click Load models, then select a model that the remote Agent allows. Leave it unselected to keep the remote default behavior.

The remote model list depends on the access permissions of the current connection credentials. If the remote Agent does not support model selection, keep the default behavior. If a selected model becomes unavailable, reload the list and select an available model, or switch back to the default behavior before saving.

After completing the settings, click Save MCP. The platform uses the credentials to read the Agent Card and checks whether it provides a compatible A2A 1.0 JSON-RPC interface. The token is stored encrypted and used by the server when accessing the remote Agent.

Associate the connection with an Agent and verify calls​

  1. On the Agent page, create an Agent or edit one you have permission to manage.
  2. In the MCP Services configuration step, find and select the A2A Remote Agent connection you just created, then save the Agent. Confirm that the connection is enabled.
  3. Start a new session with that Agent. In your request, specify which remote Agent should receive the delegated task and what it needs to do.
  4. Review the execution process and confirm that a tool call to the remote Agent appears and returns a result. If the remote Agent needs more information, continue replying as prompted.

For example, if the connected remote Agent is used for proofreading, enter:

Please call the proofreading Agent to check the following text for spelling errors and explain the corrections: The campaign will strat this Friday. You are welcome to join.

You can describe the remote Agent’s applicable tasks and expected output in the Agent’s instructions to help it delegate when appropriate. Saving a connection or loading the tool list only confirms that the corresponding configuration or tool discovery step succeeded. For your first use, verify the result through an actual delegated task.

FAQ and limitations​

SymptomChecks and solutions
Cannot read the Agent Card or save the connectionCheck that the complete Card URL is entered, the token is valid, and the service provides an A2A 1.0 JSON-RPC interface. Confirm that the platform can access the Card and its declared service URL. For a private network or HTTP URL, check the corresponding access switch.
Authentication fails when an external platform reads the AE Card or calls a taskConfirm that both Card retrieval and task requests include the Authorization and A2A-Version: 1.0 headers. Check that the user who owns the token has permission to access the Agent and that the Agent is enabled.
Cannot load the model list or the selected model is unavailableCheck the URL, token, and remote model selection capability. Reload the list and select a model available to the current credentials. To leave the model unspecified, select Keep remote default behavior.
A message says the A2A Bearer Token cannot be savedIf the message says that credential encryption has not been configured for the service, contact an administrator to complete the service configuration, then try again.
The connection is saved, but the Agent does not call the remote AgentConfirm that the connection is enabled and selected under MCP Services for the target Agent. Explicitly delegate a task in a new session. If a call occurs but execution fails, follow the returned message to check the remote service, permissions, and network. If necessary, contact an administrator to check connectivity from the execution environment.

The current connection supports A2A 1.0 JSON-RPC and Bearer authentication. It is not compatible with A2A 0.3, and regular MCP, REST, or gRPC connection settings cannot be used directly. Capabilities such as attachment transfer and streaming responses depend on what both parties actually support and declare. Start with a text task to verify the connection.

Was this page helpful?