Know who’s about to leave your Skool — before they do.

Your agent pulls each member's activity through MySkool — posts, comments, last login, level, course progress — and ranks them by whatever rule you give it. You decide what “going cold” means; we give the agent the data to see it.

MySkool acts as your own authenticated Skool account, which you consent to when you connect it, and throttles writes to a human pace. We never touch accounts you don't own. That said, this rides an unofficial surface — read the disclaimer below.

No. MySkool has no inbox, no pipeline, no feed of its own. It gives the agent you already talk to a way to read and act on your community, so the work happens inside that conversation.

Skool has no public API. We track their internal api2 surface and the Next.js data payloads, with defensive parsers and a 'shape changed' alarm (skool_shape_changed) so you get a clear error instead of silent garbage when Skool drifts.

As long as Skool keeps it valid. We re-verify connections on a schedule and flip them to 'expired' before your calls start 401-ing, so you're told to reconnect early.

60 requests/minute per key and 30,000 requests/month per account, reported through standard X-RateLimit-* and X-Quota-* headers. One plan, so the limits are an abuse guard, not an upsell.