Skip to main content
An integration says what Darwin supports. A connection says which external account one AI has authorized.

Authorization flow

  1. Create a Darwin-hosted authorization session for the AI and toolkit.
  2. Complete provider consent in the popup or redirect flow.
  3. Confirm the sanitized connection identity and granted toolkit state.
  4. Assign a compatible skill and preserve reviewed-action requirements.
Capability availability requires an active connection, an active toolkit grant, sufficient provider scopes, a compatible assigned skill, and the current approval policy.

Disable or remove access

Disabling a toolkit immediately blocks that capability in Darwin while leaving unrelated grants active. Removing the provider account disables every grant, removes stored credential material, and attempts provider revocation. Applications see only sanitized account identity and grant status. Provider credentials and internal account identifiers never enter the public API.
Use an integration to answer “what can Darwin connect to?” and a connection to answer “what has this AI authorized?”