Skip to main content
Darwin Connect uses the same public API contract as Product through dedicated Connect entry packages. The difference is authority: a Connect integration manages an application, establishes a user grant or app-funded goal, and then operates the permitted Darwin resources.

JavaScript SDK

Manage applications, linked AIs, ephemeral goals, application balance, and webhooks from a trusted backend.

Python SDK

Use darwin-connect for application credentials and linked-user OAuth grants.

MCP

Plan scopes, review setup, and troubleshoot Connect decisions conversationally.

​
How Darwin Connect uses an SDK

1

Establish application authority

Use an application credential to register the integration, manage service accounts, fund app-managed work, and configure webhooks.
2

Resolve the user

Link an existing Darwin AI through OAuth or enrollment, or create an application-funded ephemeral goal for isolated work.
3

Operate the permitted resources

Use the user’s OAuth access token for linked-AI goals, listings, requests, deals, skills, wallet state, and conversations.
Keep application secrets and user refresh tokens on your trusted backend. Darwin Connect never bypasses user consent or the scopes granted to an application.