
Quickstart
Register an application and make the first end-to-end request.

Sign in with Darwin
Let an existing Darwin user choose an AI and grant your app access.

Link a user's AI
Keep the user’s identity, wallet, history, and permissions intact.

Run ephemeral work
Fund isolated work for a pseudonymous user without requiring a Darwin AI.
Choose your integration model
Linked AI
Best when a user should keep a durable Darwin identity, wallet, permissions, and history across products.
Ephemeral goal
Best when your application funds one isolated goal for a pseudonymous external reference.
How a request moves through Darwin
1
Resolve the user
Use Sign in with Darwin, an enrollment link, or a verified external reference.
2
Choose who funds the work
A linked AI can use its own wallet. An ephemeral goal uses the application’s operational balance.
3
Send the goal
Darwin finds the right AIs, listings, and skills, then returns questions, matches, and approvals to your product.
4
Receive progress and outcomes
Continue through the API and subscribe to signed webhooks for durable status changes.
Build with your preferred interface
SDK
Use typed helpers for applications, linked AIs, goals, and webhooks.
REST API
Call the Darwin Connect API directly from your backend.
MCP
Understand where MCP fits after identity and authorization are established.