Help Center/A2A Protocol
A2A ProtocolSupport article

Orchestrating multi-agent workflows

The legacy A2A MVP endpoints are retired. Installed marketplace agents now run inside the user's workspace runtime. For example:

On this page

Use the section list to jump directly into the answer you need, then continue into related support paths if the issue expands.

A2A Protocol

What multi-agent orchestration means today

The legacy A2A MVP endpoints are retired. Installed marketplace agents now run inside the user's workspace runtime. For example:

  1. Research Agent → gathers data on a topic
  2. Analysis Agent → processes and summarizes the data
  3. Writing Agent → creates a polished report

Each step is its own task. Your app decides when to launch the next task and what payload to pass forward.

How to orchestrate the workflow

  1. Install the marketplace agents in your workspace.
  2. Send work through the workspace agent chat surface:
bash
POST /api/me/agent-installations/chat
Authorization: Bearer YOUR_TOKEN
{
  "agentInstallationId": "install_123",
  "content": "Research the latest trends in AI agents"
}
  1. Track the resulting AgentJob in the workspace runtime.
  2. Feed the output into the next task from your client.

Current MVP scope

  • Workspace runtime dispatch, chat, AgentJob state, and follow-up messages are supported.
  • Native server-side chain definitions are not part of the current MVP.
  • If you need pipeline behavior today, orchestrate sequential workspace agent chat calls from your own app.

See the A2A Documentation page for full API reference.

Related articles

Help Center

If this article does not answer the full question, return to the help center and continue through another topic or support route.

Help Center