Skip to main content

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.

This glossary aligns Agent-to-Agent (A2A) vocabulary with what you see in Graph Studio, Agent Registry, and the gateway. For protocol details beyond Phinite, see the official A2A protocol specification.

Industry terminology map

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 Agent-to-Agent 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
Promote to LiveAgent Cards / promote actionPUT .../promote-live — demotes other live builds for the same flow
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
Agent GraphFlowThe workflow backing the registered agent

UI labels vs documentation terms

Product UI labelPreferred docs termWhere it appears
Agent BlockAgent NodeBrowse / Discovery panel when attaching registry agents on the canvas
FlowAgent GraphProject and Studio navigation (same underlying workflow)
OrganisationOrganisationRegistry filters and Agent Card visibility (British spelling in UI)
When writing integrations or internal runbooks, prefer Agent Node and Agent Graph for consistency with Graph Studio agent nodes documentation.

MIME input and output modes

Skills and registry filters declare which content types an agent accepts and returns. Phinite supports the following MIME types in Agent Registry filters and skill configuration:
MIME typeTypical use
text/plainPlain text messages
text/markdownMarkdown-formatted text
text/htmlHTML content
application/jsonStructured JSON payloads
application/pdfPDF documents
application/octet-streamBinary or opaque payloads
image/png, image/jpeg, image/webpImage inputs or outputs
video/mp4Video content
audio/mpeg, audio/wav, audio/ogg, audio/aac, audio/mp4Audio content
Input modes describe what callers may send to a skill; output modes describe what the agent may return. Discovery mode on an agent node can filter registry agents by matching input and output MIME modes at runtime.

Overview

End-to-end Agent Registry concepts and workflow.

Endpoints & lifecycle

Hosted URL patterns, test vs live, and promotion.

Registry agent nodes

Browse vs Discovery on the canvas.

Platform glossary

Broader Phinite terminology (assistants, builds, tools).