Skip to main content
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 Build to skills, discoverability tags, visibility, and a hosted A2A URL that external systems and other agents can call.

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 Registry catalog light theme

Agent Registry — search, filter, and inspect exposed A2A agents

​
What the Agent Registry is

Use Agent Registry when you want to:
  • Publish an Agent Graph as a callable A2A service — not only run it via channels or triggers.
  • 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

​
Browse the catalog

Open Agent Registry from the workspace sidebar (workspace.sidebar.agent_registry).
Agent Registry catalog with filters

Registry catalog — filter by visibility, status, and MIME modes

​
Filter dimensions

  1. Open Agent Registry from the workspace sidebar.
  2. Search or apply filters to narrow agents.
  3. Select an agent to view Agent Card details and hosted URL.
  4. Use TEST URLs for validation; LIVE URL after Push to Prod.

​
Compose with registry agent nodes

Registry agent nodes let a Master Agent call other exposed A2A agents from your organisation or public catalog.
Registry Browse and Discovery panel in Graph Studio

Browse and Discovery — attach registry agents on the canvas

​
Attach via Browse

  1. Open Graph Studio and select a Master Agent node.
  2. Add or select an unconfigured agent node beneath it.
  3. Open the Browse panel.
  4. Search and filter agents (same dimensions as the catalog).
  5. Select an agent card and review preview (hosted URL, skills, build status).
  6. Add to canvas; configure exported tools and env in the Configuration sub-view.
  7. Save — node stores agent_node_type: "browse" and a2aregistryid.

​
Attach via Discovery

  1. From the registry panel, switch to Discovery mode.
  2. Set filters: Visibility, Deployed (Live/Test), Input/Output MIME modes, Tags, Auth.
  3. Click Save Filters — creates a Discovery Agent node.
  4. Configure Discovery API key if prompted.
  5. Save the graph.
In Discovery mode, the Master Agent finds and attaches agents automatically based on saved filter criteria at runtime.

​
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.
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: 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

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.

Deploy as A2A

Expose entry point from Graph Studio Deploy dialog.