Platform Features

Everything You Need to Power Your Product with AI

A deep dive into the platform capabilities that make Manifest the infrastructure layer for AI-powered SaaS products.

REST API

The Most Powerful Channel

Embed agent interactions directly in your product's UI. The REST API gives you full programmatic control over agent conversations with real-time streaming, structured inputs and outputs, and flexible conversation management.

SSE Streaming

Real-time responses streamed to your frontend via Server-Sent Events. Keep-alive signals survive CDN timeouts.

Structured JSON Schema I/O

Define response schemas so your frontend always gets the exact data shape it expects. Compatible with OpenAI structured outputs.

Conversation Threading

Maintain context across interactions. Router mode auto-selects the right agent, or go direct-to-task for full control.

api-call.js
// Trigger agent with structured output
const response = await fetch(`/a/${teamSlug}/agents/api/post/`, {
method: 'POST',
headers: { 'Authorization': 'Api-Key mfst_...' },
body: JSON.stringify({
request_data: {
message: 'Analyze order #12345'
},
response_schema: {
type: 'object',
properties: {
summary: { type: 'string' },
actions: { type: 'array' }
}
}
})
});
SSE Stream: event: response
{ "summary": "Order shipped via FedEx...",
"actions": ["Send confirmation"] }
Two Ways to Connect Tools
1
Connect Existing MCP Servers

Point to any MCP-compatible endpoint by URL. Add authentication. Your agent can use your tools immediately.

2
Build Custom MCP Servers

Use our built-in IDE to quickly write integrations to your existing APIs, or sync from GitHub. Deployed on Cloudflare Workers for Platforms with per-customer isolation.

Your Product Data ←→ MCP Server ←→ AI Agent Customer

MCP Integration

Connect Your Workflows to Your Data

MCP (Model Context Protocol) is the open standard for connecting AI agents to external tools and data sources. Think of it as USB-C for AI. Manifest speaks it natively.

Agent needs to look up order history? MCP tool.

Agent needs to update a CRM record? MCP tool.

Agent needs to trigger a workflow in your system? MCP tool.

Per-workflow tool filtering and role-based access control on every tool call.

White-Label Channels

Your Brand on Every Channel

One agent powers every channel simultaneously. Each channel is fully white-labeled — your customers interact with your agent under your brand, not ours. Multi-language support included out of the box.

Channel Key Capabilities White-Label Story
REST API
SSE streaming, structured JSON Schema I/O, conversation threading, router + direct modes, file attachments Your API, your auth, your schemas
Slack
Threaded conversations, slash commands, file handling, multi-workspace, user authentication Your branded Slack app — customers install yours, platform handles everything
Email
Inbound processing, thread tracking, HTML templates, task-specific addresses, attachment handling Your domain, your templates, your reply-to addresses
Discord
Guild integration, verification workflows, private channels, role assignment Your Discord bot
Webhooks
Accept arbitrary JSON, auth secret verification, intelligent routing Your webhook URLs, any integration
Canvas
Single-line JS embed, full screen or chat widget modes, conversation threading Native chatbot drop-in — no code required, fully white-labeled
SMS
Two-way messaging, conversation tracking, multi-language support Your number, your brand
Phone
Inbound and outbound voice, multi-language support Voice-powered agent interactions under your brand
WhatsApp
Rich media, conversation threading, multi-language support Engage users on the world's most popular messaging platform
Scheduled
Cron, interval, daily, weekly, monthly, run-once triggers Background automation for your customers

Multi-Tenancy

Multi-Tenant by Design

The entire architecture — Products, Sub-Teams, isolated workflow environments — is purpose-built for SaaS embedding. Role-based access and permissions are built in from the start.

One API call creates an isolated customer workspace for workflow execution, with API credentials and member provisioning.

Complete data isolation: workflow executions, events, MCP tool calls, and conversation state are all scoped per customer.

Workflow propagation: update a workflow once, every customer's agent updates on the next interaction. No redeployment.

External ID mapping: store your system's customer IDs alongside provisioned teams for bidirectional sync.

Architecture
Your Product
Workflow: Support Workflow: Analytics
Provisioning API
Customer A
Support
Analytics
Isolated data
Customer B
Support
Analytics
Isolated data

Ready to get started?

Ship AI agents in your product this week. Get early access to the platform and start building.