Skip to main content
Deploy as A2A exposes an Agent Build with an Agent Card — the agent’s public identity. Create a Build before opening the deploy wizard (Deploy stays disabled until one exists).

​
Prerequisites

Before you expose an Agent Graph:
  1. Save the graph and create at least one Agent Build (Builds overview).
  2. Hold Developer role or higher for Graph Studio save/build actions.
  3. Have permission to call registry APIs (assistants.flows:create via gateway POST /a2a-registry).
  4. Publish any tools referenced by the graph — unpublished tools show Publish in the build step.

​
Open the expose flow

  1. Open Graph Studio for the Agent Graph.
  2. Click Deploy — the Deploy Agent Build modal opens.
  3. Select a Build (immutable snapshot of graph + tools).
  4. Choose Deploy as A2A (other tabs: Deploy to Channel, Deploy as Chat API).
  5. Review the three-step A2A path shown in the modal, then Continue to A2A with Build N.
  6. Existing LIVE / TEST endpoints for this agent appear at the bottom of the modal when already registered.
Deploy Agent Build modal with Deploy as A2A tab

Deploy Agent Build — Deploy as A2A

​
What Deploy as A2A does

You can also open graph-scoped cards from Studio → Agent Cards under Graph assets.
Agent Cards sidebar in Graph Studio

Agent Cards — Active deployments and versions

Use Create New Build in the deploy modal when you need a fresh snapshot before exposing.

​
Wizard steps (after Continue to A2A)

Primary actions: Next (steps 1–2), Attach Agent Card (step 3).

​
Step 1 — Agent Build Config

Agent Build Config step with graph and tools

Expose wizard — confirm Agent Graph and tool versions

  1. Agent Graph accordion — select the saved graph version (name, version number, notes, timestamp).
  2. Tools Associated accordion — select published tool versions. Unpublished tools show Publish inline.
  3. Validation requires a selected graph version and at least one published tool when tools exist on the graph.

​
Step 2 — Additional Config

  1. Toggle Export value for agent version to include predefined tools, MCP tools, or env variables in the registry build.
  2. When enabled, use tabs Predefined, MCP, and Env — search Search tools and variables…
  3. For each exported row, provide a description (required).
See Build export configuration for when to export credentials for external callers.

​
Step 3 — Configure the Agent Card

Agent Card configuration step

Agent Card identity — skills, tags, and visibility

Wizard copy: Agent Card is the identity of your agent on the Internet.
  1. Edit fields as needed.
  2. Click Attach Agent Card — calls POST /a2a-registry?workspaceid={workspaceId} with wizard payload.

​
After registration

On success:
  1. Note the Agent Registry ID and hosted A2A URL (LIVE builds use the short {flowId} path — Endpoints & lifecycle).
  2. The build is available to Test.
  3. Open Studio → Agent Cards or the workspace Agent Registry to inspect the entry.
  4. Promote to live from Agent Cards when ready for production routing.
One LIVE version per Agent Graph per workspace. Push To Prod demotes the previous LIVE row to TEST.

Endpoints & lifecycle

TEST vs LIVE URL patterns and promotion.

Browse the catalog

Find and inspect registered agents.

Agent Cards

Compare builds and Push To Prod.

Build export

Export tools, MCP, and env into the build.