Overview
Smooven is a unified notification platform that consolidates SMS, RCS, Push Notifications, Email, and In-App Messaging into a single API. It is designed for both human developers and autonomous AI agents.
The problem Smooven solves
Section titled “The problem Smooven solves”Most notification infrastructure today is fragmented. You need one provider for SMS, another for email, a third for push notifications, and yet another for RCS. Each comes with its own API, authentication pattern, pricing model, and reliability guarantees.
For teams building AI-powered applications, the problem is worse. Traditional notification APIs require explicit channel selection, rigid message formatting, and synchronous responses. None of that works well for autonomous agents that need to communicate with humans.
How Smooven works
Section titled “How Smooven works”Smooven provides a single API endpoint that accepts either:
- Direct channel requests: specify the channel (SMS, RCS, push, email, or in-app), recipient, and message content.
- Intent-based requests: describe what you want to achieve in natural language, and Smooven determines the best channel, format, and delivery method automatically.
// Intent-based: Smooven picks the best channelPOST /v1/agent/notify{ "intent": "Remind Sarah about her appointment tomorrow at 2pm", "urgency": "normal", "context": { "user_id": "sarah@example.com" }}Core concepts
Section titled “Core concepts”| Concept | Description |
|---|---|
| Players | Recipients in your system. Each player has associated channels (phone number, device token, email, etc.) |
| Channels | The delivery mechanism: SMS, RCS, Push, Email, or In-App |
| Smart Routing | Smooven’s engine that selects the optimal channel based on user preferences, device capabilities, and cost |
| Dual-Key Auth | App ID (public, used in SDKs) plus Secret Key (private, used server-side) |
| Templates | Reusable message formats with variable substitution |
Supported channels
Section titled “Supported channels”| Channel | Requires App | Rich Media | Cost | Best For |
|---|---|---|---|---|
| SMS | No | No | Per message | OTPs, alerts, universal reach |
| RCS | No | Yes | Per message | Branded engagement, interactive flows |
| Push | Yes | Limited | Free | Activity updates, promotions, re-engagement |
| No | Yes | Per message | Newsletters, detailed confirmations, marketing | |
| In-App | Yes | Yes | Free | Contextual messages within your application |
Next steps
Section titled “Next steps”- Quickstart: send your first notification in under 5 minutes
- Authentication: set up your API keys
- Smart Routing: learn how Smooven picks the best channel