For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • What are capabilities?
  • Add a Capability
  • Choosing Capabilities
  • Surface orchestration
  • Managing Capabilities
  • Reusing Capabilities
  • Next steps
Products & Surfaces

Adding Capabilities to a product

Was this page helpful?
Previous

Connecting external agents

Next
Built with

Capabilities are the Flows and Agents you attach to a Product to make them available through Surfaces. Add Capabilities to define what your Product can do.

What are capabilities?

When you add a Flow or Agent to a Product, it becomes a Capability—an AI function that users can access through the Product’s surfaces. A single Product can have multiple Capabilities.

Add a Capability

  1. Open your Product from the Products list.
  2. Locate the Product Capabilities section (in either the List view or Visual view).
  3. Click the Add Capability button.
  4. In the Add Capability slide-over, choose how you want to add the Capability (e.g., New Agent, New Flow, External A2A, or Use Existing).
  5. Follow the prompts to configure and add your Capability.

The Capability now appears in your Product’s Capability list and is available through all active Surfaces.

Choosing Capabilities

Select Capabilities that work together to solve a user problem. For example, a customer support Product might include:

  • FAQ answering Flow
  • Order status lookup Agent
  • Escalation routing Flow

Each Capability handles a different aspect of customer support.

Surface orchestration

How Capabilities are invoked depends on the surface’s orchestration mode:

  • Single capability — User chooses which Capability to call (e.g., via API endpoint path)
  • Orchestrated — The Product routes requests to the appropriate capability automatically

For details, see Surface orchestration modes.

Managing Capabilities

To remove a Capability from a Product:

  1. Click the more menu (⋯) next to the Capability
  2. Select Remove from Product
  3. Confirm removal

Removing a Capability from a Product doesn’t delete the underlying Flow or Agent—it just disconnects it from that Product.

Removing a Capability makes it unavailable through all Surfaces on that Product. Users relying on that Capability will get errors if they try to access it.

Reusing Capabilities

The same Flow or Agent can be a Capability in multiple Products. For example, your “sentiment analysis” Flow might be used in:

  • Customer support Product
  • Social media monitoring Product
  • Content moderation Product

Changes to the Flow apply to all Products that use it.

Next steps

  • What are Surfaces? to understand how users access Capabilities
  • Setting up a chat Surface for web deployment
  • Product views to visualize Capability connections