Skip to main content
A2A Registry

​
What the Agent Registry is

The Agent Registry is your workspace catalog of Agent Cards—registered metadata and hosted endpoints for agent graphs you expose over the Agent-to-Agent (A2A) protocol. Each registry entry ties a published agent graph build to skills, discoverability tags, visibility, and a hosted A2A URL that external systems and other agents can call. Use Agent Registry when you want to:
  • Publish an agent graph as a callable A2A service (not only run it inside a single assistant).
  • Discover agents across your organisation—or, when visibility is public, from compatible clients with a valid API key.
  • Compose multi-agent workflows by attaching registry agents to a master agent node in Browse or Discovery mode.
  • Call registry agents from Claude using the Phinite Connector (discover_agents, call_agent, and credential setup).

​
End-to-end workflow

StepWhereOutcome
1. DesignGraph StudioAgent graph with prompts, tools, and routing
2. PublishPublishingVersioned build ready to expose
3. ExposeExpose your flowAgent Card + registry ID + test hosted URL
4. BrowseAgent Registry catalogSearch, filter, inspect skills and endpoints
5. ComposeRegistry agent nodesCall a specific agent (Browse) or auto-match filters (Discovery)
6. PromoteAgent CardsOne live build per agent graph per workspace

​
Access and environment

Agent Registry sidebar entry, Configure Agent in Graph Studio, and related expose flows are available when the app runs in a local or dev environment (NEXT_PUBLIC_APP_ENV is local or dev, or NODE_ENV is development). Production rollout may differ—confirm with your administrator.
Sidebar permission: workspace.sidebar.agent_registry (legacy alias workspace.sidebar:agent_registry). Routes:
  • Workspace catalog: /{organisation}/workspace/{workspaceId}/agent-registry
  • Project Agent Cards (builds): /{organisation}/workspace/{workspaceId}/projects/{projectId}/agent-cards
  • Graph Studio (expose entry): .../projects/{projectId}/studio

​
Terminology

Phinite maps industry A2A vocabulary to product labels as follows:
Industry / A2A termPhinite UI / APIMeaning
Agent CardAgent Card (wizard step 3)Public identity: name, description, skills, tags, visibility
Agent RegistryAgent Registry sidebarWorkspace catalog of registered A2A agents
A2A endpoint / Hosted agent URL/api/v1/ai/a2a/{flowId} or .../{registryId}Callable agent over the A2A protocol
SkillsSkills in wizardCallable capabilities with input/output MIME modes
Discoverability tagsDiscoverability TagsMetadata for search and Discovery filters
Deployment statusTest / Live badgestest = validation build; live = production (one live per flow per workspace)
VisibilityPublic / Organisationpublic = any A2A client with a valid API key; organization = same organisation only
Browse modeBrowse tab on agent nodeMaster agent calls a specific registry agent
Discovery modeDiscovery tab on agent nodeMaster agent auto-selects agents matching saved filters at runtime
Some canvas labels still say Agent Block (for example in the browse panel); documentation uses Agent Node as the preferred term. See the Agent Registry glossary for MIME modes and API field names.

​
Next steps

Invoke from Claude

Install the Phinite Connector, discover agents, and run tasks from Claude.

Expose an agent

Register an agent graph with the three-step Expose wizard.

Registry agent nodes

Browse vs Discovery on the Graph Studio canvas.

Browse the catalog

Search, filter, and inspect registry entries.

Agent Cards & builds

Manage test and live builds; push to production.

Endpoints & lifecycle

Hosted URL patterns, auth, and promote-live.

Glossary

Industry terms, MIME modes, and UI label mapping.