Skip to main content
Publishing in Phinite covers two related actions: publishing tool versions so they can be pinned in builds, and promoting Agent Builds (and A2A Agent Cards) across DEV → UAT → PROD.
Unpublished tools appear with a Publish action in the Build Agent dialog. You cannot create a build that references unpublished tool versions.

​
Publish tools before building

  1. Open Graph Studio for the Agent Graph.
  2. Click Build (graph must be Saved).
  3. In the TOOLS section, locate any row showing Publish.
  4. Click Publish for each unpublished tool — this creates a versioned tool artifact the build can pin.
  5. Confirm all required tools show published versions, then Create Build.
See Build configuration for optional export of additional tools into the build or Agent Card version.

​
Publish and deploy an Agent Build

  1. Validate the graph — run Test in Studio and review Observability logs for errors.
  2. Create the build with a clear Description (audit trail for your team).
  3. Assign DEV — deploy to a channel, trigger, or A2A TEST endpoint (Deploy).
  4. Smoke test in DEV — confirm env variables and integrations resolve correctly.
  5. Promote to UAT — reassign the build or switch webhook URLs to the UAT endpoint.
  6. Promote to PROD when approved — update production webhooks and env-scoped credentials.
Document build descriptions with what changed in the graph or tools. Future you (and auditors) will thank you when comparing rows in Agent Builds.

​
Publish A2A Agent Cards

A2A exposure adds a registry layer on top of builds:
  1. Expose your Agent Graph — creates a TEST Agent Card version.
  2. Validate against the TEST hosted URL (Endpoints & lifecycle).
  3. Push To Prod from Agent Cards — promotes to LIVE public URL.
Production A2A promotion and some workspace deploy actions require elevated roles. Coordinate with workspace admins before pushing LIVE.