Apify Actors run in isolated containers with no persistent session — there is no concept of “who is logged in.” This recipe shows how to use Apify’s built-in user identity as the key into Scalekit’s OAuth token vault, so each user who runs your Actor connects their own third-party accounts, and tokens survive across runs without any user-managed input fields.
Machine-to-machine access tokens are JWTs signed by Scalekit. Your API verifies signatures using the published JWKS at /keys, then authorizes requests using the scopes embedded in each token. This cookbook ties those ideas together end to end.
Install the Scalekit Auth Stack plugin into your coding agent and paste one prompt. The agent scaffolds OAuth handling, token management, and connected account logic so you can start writing agent logic immediately.
When your customer’s identity provider pushes more users than your plan allows, SCIM won’t stop it. This cookbook shows how to track provisioned users per organization, block creation when the quota is hit, and notify admins — using two webhook events and a counter in your database.
As AI agents raise the velocity of code changes, the volume of open PRs on any team keeps growing. This recipe builds a Render Workflow that finds the five most-discussed open PRs in a repository, reads their diffs and comment threads, and generates a plain-language paragraph per PR — written for a team lead or manager. Each team member runs the same workflow with their own user ID; Scalekit’s token vault handles per-user GitHub OAuth so the agent acts as the right person every time.
