All help articles
Help articles (128)
Payment fees explained
What it costs to collect money through your Overskill app. Payments run on Whop. You pay Whop's published rates.
Test your checkout without paying
Run a real $0 purchase through your own checkout to confirm the whole buy → sign in → access flow works — before a single customer arrives.
Overskill API errors and how to handle them
What 401s, rate limits, credit exhaustion, and other API errors look like — and the right way for your code (or your agent) to respond.
Publish your app to Google Play
Turn your Overskill app into a real Android app on Google Play — published under your own Google account, with your own name and icon.
Version history and rollbacks
Every change is a saved version. Roll back, restore, or compare any version with a click.
The Overskill badge on your app
The small badge in the corner of your app — what it is, how to move it, how to hide it, and the one step people forget.
Reusing work from another Overskill app
Attach one of your other Overskill apps to a chat so the AI can look at how you solved something there and build the same thing in the app you're working on.
Importing data into your app
Bring in data from a spreadsheet, CSV file, or another tool. Useful for migrating from existing systems.
My users get a 401 when they log in
The
Paying affiliates to promote your app
If you sell your app through Overskill Payments, it already has an affiliate program built in — commissions are tracked on your product's referral links and paid automatically, and your affiliates don't need an Overskill account.
Editing vs. rebuilding — which is more credit-efficient?
Editing what you already have is almost always cheaper than rebuilding from scratch. Here's why, and the few times a fresh start actually wins.
Using Overskill API webhooks
Get pushed events for generations, deployments, and app users. Registration, the event catalog, signature verification, and testing deliveries.