Managing the Capability Registries
Every reusable thing an agent can attach — a connection, a tool, a skill, and so on — lives in its own registry under Agents. Registries share a common create/edit/share pattern; this page covers that pattern once, then what's distinctive about each registry.
Before you begin
Creating or editing most items requires permission to edit the capability library. Submitting an item for global review requires a separate permission.
Open a registry
Select Connections, Memory Providers, Tool registry, Skill registry, Prompt registry, MCP registry, A2A registry, or Guardrail registry in the Agents left sidebar.
Create an item
Every registry's create flow starts the same way — select the button to add a new item (labeled Create, Add, or specific to the registry, such as New MCP source), then fill in at least a Name and, on most, a Description. What comes next differs by registry — see the table below.
| Registry | What's distinctive | Notes |
|---|---|---|
| Connections | Pick a provider first, then fill in what it requires — a model, and depending on the provider, an endpoint URL, deployment name, API version, base URL, or API key. An Advanced section exposes temperature, top P, top K, seed, stop sequences, reasoning effort, and safe-prompt, where the selected model supports them. | Model and sampling parameters live here, not on the agent. |
| Memory Providers | The native provider needs only a Name and Description — no credentials. Some providers show a Coming soon tag and aren't connectable yet. | |
| Tool registry | Set a Base URL, optionally add authentication headers, then add one or more Actions — each with a name, HTTP method, path, description, and optional parameters (name, location, type, and whether it's required). | The most detailed of the registry forms — a tool can have several actions, each with its own parameters. |
| Skill registry | A single Instructions field — markdown the agent follows whenever the skill is linked. | |
| Prompt registry | A single Content field — markdown appended to the agent's system prompt whenever the prompt is linked. | |
| MCP registry | A Server URL, and an Authentication setting of None, Bearer token, or OAuth. Choosing OAuth lets you Discover from server, or enter the authorization, token, and registration endpoints yourself; registering or entering a client happens after the source is first saved. | See Deploying an Agent in a Workflow for how an OAuth-backed MCP source gets connected per agent. |
| A2A registry | An AGENT CARD URL for the remote agent. | |
| Guardrail registry | A Kind — Deterministic, Structural, Groundedness, Tool use, Classifier, Self-critique, or Dialog quality — and a Stage of Input, Tool use, or Output. Only an Input-stage check can block a run; the others are recorded but never stop it. Fields below change with the kind you pick — a regex pattern and match mode for Deterministic, a JSON schema for Structural, a citation requirement for Groundedness, a list of forbidden tool names for Tool use, or a rubric prompt and pass threshold for the three LLM-judged kinds. |
Share an item with your organization
Some registry items start visible only to the agent that created them. To make one available to every agent in your organization:
- On the item's row, select Share with organization.
This applies immediately — there's no confirmation step.
Submit an item for global release
Global release makes an organization-visible item available to every organization on the platform. This requires a separate permission from ordinary editing.
- On an organization-visible item's row, select Submit for global review (or Resubmit for global review, if a previous request was rejected).
The item's visibility tag changes to Pending global review while a reviewer decides. See Global Review for what happens next.
Visibility tags
| Tag | Meaning |
|---|---|
| This agent only | Visible only to the agent that created it |
| Organization | Visible to every agent in your organization |
| Global | Visible to every organization on the platform |
| Pending global review | Submitted for global release and awaiting a decision |
| Global review rejected | A global-release request was turned down — hover the tag for the reviewer's reason, if one was given |
Next steps
- Attaching Capabilities — attach a registry item to an agent.
- Global Review — approve or reject a pending global-release request.