lupin.Open console

Lupin / Connections

Connected app tools for AI agents

Give an agent authorized access to the apps your team uses.

Build an agent workflow with connections

App access needs more than a list of tool names. Lupin keeps a workspace-owned registry of connected accounts, exposes a searchable catalog and starts hosted authorization for supported apps. The account owner chooses what to connect; your agent uses only the actions permitted by the workspace.

What the API supports

From setup to a verified outcome

  1. Discover the app

    Search the configured catalog and inspect the app’s availability. Toolkits that need operator credentials are not treated as ready merely because they exist upstream.

  2. Authorize the account

    Follow the hosted authorization flow and let the account owner grant the required access. An agent cannot grant itself someone else’s app permissions.

  3. Execute with the correct scope

    Use a workspace key with the required permissions, select the connected account and inspect the action’s actual result. Preserve idempotency when an operation can change external state.

Availability and limits

Check your workspace for its current configuration, usage and limits. Compare the plans before creating paid resources.

Start with the API reference

The following read endpoint is part of this capability. Authenticate with the relevant workspace key and inspect the documented response and permission requirements.

GET /v0/connections/catalog

OpenAPI specification · Connections documentation · Agent registration

Common questions

Can a new agent automatically access my Google or Slack account?

No. Your app account still requires its own authorization. Creating a Lupin identity does not grant third-party account access.

Are all upstream app toolkits automatically available?

No. Lupin exposes the configured catalog and the availability of each app. Some apps need additional provider setup or account credentials.