All articles
20 articles
Using OverSkill from AI agents (Claude, Cursor, Codex)
OverSkill is built for AI agents to use. Here's how to wire up Claude, Cursor, Codex, or your own agent.
What are credits?
Credits are how OverSkill measures the AI work you use. Here's what one credit gets you and how to read the meter.
How your app's users sign up
Add a sign-up flow to your app in one prompt. Customize it later. Users can sign up with email or social login.
Do your users need an OverSkill account?
No — your users never pay anything and never need the paid account you build with. They sign in with a free OverSkill account that works across every OverSkill app. Here's the difference.
Restricting access to paid users
Gate parts of your app — or the whole thing — behind a subscription or one-time purchase.
Connecting your own domain
Use your own web address — like myapp.com — instead of the default one.
Do my users get a real username and password?
Yes. Your app's users sign in with a real email and password (or social login). OverSkill securely hosts the password setup, storage, and reset for you — so you get battle-tested accounts without building risky login code yourself.
Roles and permissions in your app
Give different users different access levels — admins, editors, viewers, custom roles.
Using OverSkill API webhooks
Get pushed events for generations, deployments, and app users. Registration, the event catalog, signature verification, and testing deliveries.
Credits in your published app: who pays for AI usage
If your live app has AI features, your visitors using them spends YOUR credits — once per action. Here's how it works and how to control it.
Build your first app in 3 minutes
A start-to-finish walkthrough of your first build. Copy the example prompt, watch it come together, and publish before your coffee gets cold.
Preview vs live: how publishing works
Your changes are visible to you instantly. They're visible to your users when you publish. Here's the difference.
How to ask the AI for changes
Better prompts get better results. The short guide to writing requests the AI nails on the first try.
Team roles
Know the difference between future OverSkill editor roles and the app-user roles inside your generated app.
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.
Why errors and retries still use credits
Building with AI is iterative — some generations error or need a follow-up, and those still use credits. Here's why, and how OverSkill keeps the cost low.
Working with multiple apps
Patterns for managing several apps at once — organization, naming, sharing components.
Getting started with the OverSkill partner API
Generate, manage, and deploy apps programmatically. Auth, the core call sequence, and working code in Node, Python, and curl.
Switching between teams
If you're in multiple workspaces, here's how to switch between them without signing out.
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.