Platform Integrations

Gateway Architecture

The message gateway connects platform channels to agents. When a message arrives:

1. Route resolution — Match platform + channel ID to an agent
2. Rate limiting — Check per-user and global rate limits
3. Credit check — Verify minimum $0.50 balance
4. Session loading — Create or resume conversation session
5. Flow execution — Run the agent’s CAFF flow
6. Response delivery — Send the response back to the platform

Supported Platforms

Platform	Adapter	Features
Telegram	Bot API	Text, inline keyboards, files
Discord	Bot gateway	Text, embeds, reactions, threads
Slack	Bot events	Text, blocks, file sharing
Twitter	API v2	Mentions, replies, monitoring
Reddit	API	Posts, comments, keyword monitoring

Gateway Routes

Routes map a platform channel to an agent using the key format PLATFORM:channelId:

TELEGRAM:123456789    → Agent A
DISCORD:987654321     → Agent B
SLACK:C01234567       → Agent C
TELEGRAM:*            → Agent D (catch-all)

Route Resolution Priority

1. Exact match — PLATFORM:channelId matches a specific route
2. Catch-all — PLATFORM:* handles unmatched channels on that platform

Route Requirements

• Agent must be in ACTIVE state
• User must have sufficient credits ($0.50 minimum)
• Channel must pass allowlist check (if configured)

Session Management

Sessions track conversation state per user per platform:

• Persistent chat history
• Flow variable state
• Platform-specific context (user ID, channel, thread)