What is Whisperr?

What is Whisperr?

Whisperr is an autonomous retention engine for apps, games and online stores. It scores each user's churn risk, decides who gets a message and who gets nothing, writes it in your voice, sends it through your own channels, learns from every send, and proves the lift against a holdout.

These docs show how to give Whisperr what it needs from your app: who each user is, with identify, and what they do, with track. Whisperr does the rest.

How do I install Whisperr with my coding agent?

Connect your agent to the Whisperr MCP server. It does the install in your repository and proves it with real events. You review the change. An agent without MCP follows the setup guide. You can also get a pull request from the Whisperr GitHub App or run the CLI wizard.

MCP server

https://mcp.whisperr.net/install

Add the server to your coding agent, sign in when the browser opens, then ask: Install Whisperr in this app and verify that events arrive. The agent installs the SDK, wires your events, builds the app and waits until real events reach Whisperr.

Claude Code

claude plugin marketplace add WhisperrAI/whisperr-agent-kit
claude plugin install whisperr@whisperr

Cursor, VS Code, Codex, Windsurf and othersAgent kit on GitHub

Which SDK do I use?

Use a client SDK in your web or mobile app with the publishable key (wpk_…). Use a server SDK in your backend with the server key (wrk_…) for facts only your server knows, such as payments and cancellations. Send the same user id from both, and the events land on one timeline.

Web@whisperr/web for any browser app.ReactA provider and the useWhisperr() hook.Next.jsA provider for the App Router root layout.Node.jsServer key, with Express middleware.PythonServer key, with Django middleware.PHP / LaravelLaravel service provider and facade..NETServer key, with ASP.NET Core support.FlutteriOS and Android, with Firebase Messaging push.React NativeNo native code. Works in Expo Go and bare apps.ExpoConfig plugin and push helpers for Expo apps.SwiftiOS, macOS, tvOS and watchOS.

Can I call the API directly?

Yes. Events and users go in through three ingestion endpoints at https://api.whisperr.net. The API overview lists the server-only consent and data endpoints too. If you write your own client, read delivery, retries and idempotency first: a stable $message_id on each event makes retries safe.

POST/v1/events/batch1 to 500 events→POST/v1/events/trackone event→POST/v1/identifytraits and channels→

What do I connect in the dashboard?

Whisperr sends through your own providers and reads subscription state from your billing tool.

Push providersFirebase Cloud Messaging, Apple Push Notification service, Expo Push or OneSignal.Email providersResend, Postmark or SendGrid, with your own verified sender.

BillingRevenueCat, Superwall or Adapty. One billing source per app.

What should I read before I ship?

Event designWhat to track, how to name events, one user id everywhere.Keys and limitsWhich key goes where, size limits, rate limits and errors.Contact consentWhen your app can opt a user in to email, and when your server must.

Common questions

Which channels does Whisperr send through?

Push and email, through your own providers: Firebase Cloud Messaging, Apple Push Notification service, Expo Push or OneSignal for push, and Resend, Postmark or SendGrid for email. In-app messaging is coming. SMS and voice are not available.

Which API key goes in my app?

The publishable key (wpk_…), shown as an App key in Settings → API keys. The server key (wrk_…) stays on your servers.

What does Whisperr need from my code?

Two calls: identify, which says who the user is, and track, which records what the user does. Billing events can also come from RevenueCat, Superwall or Adapty.