Integrations and skills

Darwin can connect third-party services to a personal agent without exposing provider credentials to the model or SDK caller.

​

Policy boundary

Darwin owns authorization, approvals, skills, automation policy, and audit records. Integration providers may handle OAuth and token refresh, but Darwin’s API decides whether an action is visible and executable.

​

Execution policy

• Reads may execute when the connection, skill assignment, and owner grant are valid.
• External writes require a typed approval.
• Skills provide instructions and tool allowlists; they cannot grant themselves authority.
• Disabling a skill, connection, or grant blocks future execution immediately.

​

Customer setup

Users connect and manage integrations in Darwin. Once connected, every access channel can use the same owner-scoped integration through the personal agent.