Connecting an agent to two external APIs means handling two separate OAuth tokens, two authorization flows, and two different error surfaces. This recipe shows how Scalekit manages the OAuth lifecycle for both connectors, then demonstrates two patterns for calling those APIs: fetching a token and calling the REST API directly, versus letting Scalekit execute the call through a built-in action.
Switching to a browser to look up Scalekit docs breaks your coding flow. This cookbook shows you how to configure the ref.tools MCP server so your AI coding assistant can search Scalekit documentation inline — in Cursor, Claude Code, Windsurf, or any MCP-compatible client.
Every enterprise customer wants their own IdP — Okta, Azure AD, Google Workspace. Handling SAML handshakes and per-tenant routing before you’ve shipped a feature is exhausting. This cookbook shows how to delegate that complexity to Scalekit and use Auth.js to own the session layer, so enterprise SSO is an afternoon, not a sprint.
Building a scheduling agent means coordinating authentication to two separate tools — Google Calendar and Gmail — then chaining their outputs in one workflow. Without managed OAuth, each connector requires its own token lifecycle and error-handling logic. This recipe shows how Scalekit handles auth per connector so your agent can focus on finding a free slot, creating the event, and drafting the confirmation.
Spring Boot 4.0.0 introduced stricter timeout defaults for JWT validation that can cause connection failures when verifying Scalekit tokens. This guide shows you how to configure appropriate timeouts for production environments.
