Surfaces are the ways your Product reaches users. Each Surface is a deployment channel such as a chat widget on your website, a REST API for developers, an MCP server for AI IDEs, or an email integration. You build your AI Capabilities once, then add Surfaces to make them available wherever your users are. If you are new to the platform, start with What is Runtype? for a quick overview.
A Surface connects your Product to a specific interface. When someone interacts with a Surface, such as sending a chat message, calling an API endpoint, or emailing your AI, the Surface routes the request to the right Capability in your Product.
One Product can have multiple Surfaces, so the same Capabilities can be accessed through a chat widget on your website, a REST API for your mobile app, and an MCP server for developer tools without duplicating logic.
Each Surface has its own status, draft, active, or paused, and its own API keys, so you can roll out new channels at your own pace. To learn how Surface availability fits into releases, see Product versioning and status.
An embeddable chat interface for your website or web app. You can customize the theme, welcome message, and branding to match your site. Users interact with your AI through a familiar conversational experience.
Great for: Customer support, sales assistants, onboarding guides, interactive demos. To set one up, see Setting up a chat Surface.
HTTP endpoints that let developers integrate your AI Capabilities into any application. Runtype auto-generates OpenAPI specs for your API Surface, and you can configure rate limits and API keys to control access.
Great for: Mobile apps, backend services, third-party integrations, programmatic access. For setup steps, see Setting up an API Surface.
A Model Context Protocol server that connects to AI-powered IDEs like Claude Desktop, Cursor, and VS Code. Your Capabilities appear as tools that AI assistants can discover and call directly.
Great for: Developer tools, code generation, IDE integrations, AI-assisted workflows. For setup steps, see Setting Up an MCP Surface.
An open protocol that lets AI Agents communicate with each other. External Agents can discover your Product’s Capabilities and invoke them, which enables multi-Agent collaboration across platforms.
Great for: Multi-Agent systems, AI orchestration, cross-platform Agent workflows. For setup steps, see Setting up an A2A surface.
Connect your Product to a Slack workspace so users can interact with your AI through direct messages, mentions, channels, and threaded replies.
Great for: Internal tools, team assistants, support workflows within Slack. For setup steps, see Setting up a Slack Surface.
Connect your Product to email so users can interact with your AI by sending and receiving messages. Configure inbound and outbound settings to handle conversations automatically.
Great for: Customer communication, support workflows, automated email responses.
Receive push-based events from external systems over HTTP and route them to your Capabilities. A Webhook Surface learns the payload shape from sample events, verifies provider signatures, and maps fields to your Flow inputs.
Great for: Reacting to Stripe payments, Shopify orders, GitHub events, CRM updates, and other event-driven integrations. For setup steps, see Setting up a webhook Surface.
Not sure where to start? A Chat Widget is the fastest way to see your Product in action. You can add more Surfaces later. Your Capabilities stay the same regardless of how many Surfaces you add.
Each Surface exposes the Capabilities you choose. By default, all of your Product’s Capabilities are available on a Surface, but you can enable or disable individual Capabilities per Surface for more control. For setup details, see Adding Capabilities to a Product.
When a user interacts with a Surface, routing depends on the orchestration mode:
A2A Surfaces have their own orchestration options, including delegate and managed modes, to control how skills are coordinated. For more detail, see Surface orchestration modes.