Overview
Learn how AgentKit works: tool calling with pre-built connectors and authentication for AI agents acting on behalf of users.
AgentKit gives your AI agents authenticated access to third-party apps: sending emails, reading calendars, creating tickets, querying databases, and more. Your agent calls a tool; Scalekit handles the OAuth flow, token storage, and API call.
Authentication
Section titled “Authentication”Connections are configurations you create once in the Scalekit Dashboard. A connection holds the credentials Scalekit needs to authenticate with a connector (OAuth app credentials, API keys, or service account details). One connection serves all your users.
Connected accounts are per-user instances of a connection. When a user authorizes, Scalekit creates a connected account that stores their tokens and tracks their auth state. Your agent uses a connected account to act on that specific user’s behalf.
Scalekit supports OAuth 2.0, API keys, RSA key pairs, and service accounts across all connectors.
Tool calling
Section titled “Tool calling”Connectors are the pre-built integrations your agent can use: Gmail, Slack, Salesforce, Snowflake, GitHub, and many others. Each connector exposes a library of tools ready for your agent to call.
Tools are connector-specific actions: gmail_fetch_emails, salesforce_create_record, slack_send_message. Scalekit provides the tool schemas and handles the authenticated API call. Your agent passes inputs; Scalekit injects the user’s credentials and returns structured output.
How they fit together
Section titled “How they fit together”You configure connections once. Your users authenticate to create connected accounts. Your agent calls tools; Scalekit handles the rest.
Works with your framework
Section titled “Works with your framework”AgentKit is framework-agnostic. Tool schemas work with any LLM API. Native adapters are available for LangChain, Google ADK, and MCP-compatible environments.