Documentation Index
Fetch the complete documentation index at: https://docs.phinite.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before you expose an agent graph:- Publish at least one version of the agent graph. See Agent Graph publishing.
- Hold Developer role or higher for Graph Studio save/publish actions.
- Have permission to call registry APIs (
assistants.flows:createvia the gatewayPOST /a2a-registry). - Run in a local or dev environment where Configure Agent is visible in Graph Studio (see Overview — Access and environment).
Open the expose flow
- Open Graph Studio for your project.
- Select the agent graph you want to expose.
- In the canvas header, click Configure Agent (dev environments only).
- In the Expose as Agent modal, review any existing test/live builds and hosted URLs.
- Click Create New Build to open the Expose as External Agent wizard.
The modal explains that publishing an Agent Card enables the graph as a hosted agent callable via the A2A protocol. Use See Agent builds to jump to Agent Cards for the project.
Wizard steps
The wizard has three steps. Step labels in the UI:| Step | Label | Purpose |
|---|---|---|
| 1 | Agent Build Config | Pick agent graph version and published tools |
| 2 | Additional Config | Optional export of tools/variables to the build |
| 3 | Configure the Agent card | Agent Card identity, skills, tags, visibility |
Step 1 — Agent Build Config
Confirm the Agent Config:
- Agent Graph accordion — select the flow version to register (name, version number, version notes, timestamp).
- Tools Associated accordion — select published tool versions linked to the graph. Unpublished tools show a Publish action inline.
Step 2 — Additional Config
Variables and Secrets:- Toggle Export to build to include predefined tools, MCP tools, or environment variables in the registry build.
- When enabled, use tabs Predefined, MCP, and Env and search Search tools and variables…
- For each exported row, provide a description (required).
Step 3 — Configure the Agent card
Agent Card is the identity of your agent on the Internet:
| Field | Notes |
|---|---|
| Agent Name | Read-only; derived from the agent graph name |
| Agent Description | Editable summary for catalog and A2A clients |
| Skills | Add skills with unique name, description, Input Modes, and Output Modes (MIME types) |
| Discoverability Tags | Tags help agents appear in search and Discovery filters |
| Visibility & access | Public — discoverable by any A2A-compatible agent or user with a valid API key. Organisation — visible only within your organisation |
| Auth Schemes | Platform default: use your Phinite organisation API key |
| Refine Card | Optional AI refinement (refine_prompt_for: "a2a") to improve description and skills |
POST /a2a-registry?workspaceid={workspaceId} with the wizard payload (agent_card, flowid, flow_version, assistantid, tools, and optional export config).
After registration
On success:
- Note the Agent Registry ID and hosted A2A URL (test builds use the registry ID in the path—see Endpoints & lifecycle).
- The success message indicates the build is available to Test.
- Click Go to Agent Registry to open the workspace catalog.
test. Promote to live from Agent Cards when you are ready for production routing.
Related pages
Endpoints & lifecycle
Test vs live URL patterns and promotion.
Browse the catalog
Find and inspect registered agents.