What are Products?

Products group the Flows and Agents that you expose as Capabilities. They connect those Capabilities to Surfaces, so you can choose how people and systems use them.

How Products work

Add related Flows and Agents to a Product as Capabilities. Then connect each Capability to one or more Surfaces where you want to expose it.

Every Product has two parts:

• Capabilities: the Flows and Agents that belong to the Product. Each Capability has a required name and an optional description.
• Surfaces: the deployment configurations that expose Capabilities through an interface. Surface types include Chat Widgets, REST APIs, MCP Servers, A2A Agents, Slack Channels, and Email Channels.

Each Surface has a status (draft, active, or paused). Use the status to control whether the Surface accepts requests.

Every Surface accepts both test and live credentials. Test keys and test client tokens have a daily execution cap, so use them to try a Surface. Create a live key or a live client token when you are ready for uncapped traffic.

Example: Customer Support Product

Dana manages support for Example Organization and wants to automate common requests while routing complex issues to the support team. Dana creates a Customer Support Product with these Capabilities:

• FAQ answering Flow: answers common questions using the organization’s documentation as context.
• Ticket routing Agent: analyzes incoming requests and assigns each request to the appropriate team.
• Documentation search Flow: retrieves relevant help articles when a question goes beyond the FAQ.

Dana adds these Surfaces to the same Product:

• Chat Widget: provides answers on the organization’s website.
• REST API: powers the support interface in the organization’s mobile app.
• Email Channel: receives support requests and sends responses by email.

Dana sets each Surface to active. The same Product then exposes the selected Capabilities through each configured channel.

You can reuse a Flow or Agent as a Capability in multiple Products. Each Product stores its own Capability name and description, so you can adapt how the resource appears in each Product.

Next steps

Choose a guide based on what you want to do:

• Creating a Product: create a Product and configure its initial Surface.
• Adding capabilities to a Product: connect Flows and Agents to Surfaces.
• What are Surfaces?: compare Surface types and deployment channels.
• Surface orchestration modes: choose how a Surface routes requests to multiple Capabilities.
• Product versioning and status: manage Surface availability and resource versions.
• Quickstart: Build a Social Media Post Generator as a REST API: follow a complete build-and-deploy walkthrough.