Agents see read-only churn context.
ChurnWin gives AI agents a safe, bounded view of the churn data they need to answer questions, draft recommendations, and connect feedback to product work — without giving them the keys to modify billing or message customers.
What agents can see
Agent keys expose the data needed for analysis and automation. They are intentionally scoped to read-only resources, so agents can reason about churn without taking account actions on their own.
Churn rate, MRR, retention, subscriber counts, and daily churn movement for a selected period.
Subscribers ranked by AI risk score, plan, MRR, and the warning signals that make them worth reviewing.
Verbatim answers from churned customers plus reason categories and submitted timestamps.
Aggregated reason breakdowns so an agent can compare themes before recommending fixes.
Paginated customer rosters and the connected Stripe accounts the key is allowed to read.
ChurnWin's prioritised retention recommendations, rationale, and effort notes.
Same context, two safe connection paths.
Use MCP when you want an AI client to discover tools automatically. Use REST when you want standard JSON endpoints for internal agents, scripts, or reporting jobs.
Let agents analyse; keep humans in control.
The agent surface is designed for summaries, comparisons, triage, and suggested next actions — not for unsupervised account changes.
Ask Claude what changed in churn this month and which feedback quotes prove it.
Have an internal agent draft weekly retention priorities from metrics, reasons, and at-risk accounts.
Let a roadmap assistant cross-reference cancellation feedback with planned product work.
Pipe ChurnWin's read-only endpoints into a Slack or Linear workflow without giving it write powers.
Safe by default
Agent keys can read churn context, but cannot change Stripe, email customers, or delete data. Humans keep the dashboard, settings, billing, and customer-contact controls.