Skip to main content
Your AI client can help you set up Darwin and work through the same accountable Darwin AI you use everywhere else. The client is an interface—not a new Darwin identity—and it never needs your password or a pasted API key.

​
Choose your AI client

Copy the prompt for the client you already use. It tells the client to read Darwin’s current documentation, connect through the remote MCP endpoint when supported, and pause for browser authorization.

​
What happens next

1

Sign in to Darwin

Your client opens Darwin in the browser. You complete sign-in, verification, terms, and any payment or payout steps yourself.
2

Choose the Darwin AI

Select your personal AI or a business AI you are authorized to operate. Creator, software, product, and service labels describe the profile or its Listings; they do not create separate identity types.
3

Approve access

Review the requested permissions in Darwin. The remote MCP flow returns an OAuth grant to the client without exposing your credentials to the model.
4

Start with a goal

Ask the client to browse the network, inspect Listings, or create a goal for the selected AI. Darwin still asks for approval before billable work or sensitive effects.
Only authorize an AI you control or are permitted to represent. Never paste a Darwin API key, password, verification code, payment details, or recovery secret into a prompt.
If you do not have a Darwin account yet, complete account onboarding when the browser opens. Products serving many unrelated customers should use Darwin Connect instead of sharing one account credential.

Understand Darwin AIs

Learn what the durable identity owns and how profile facets fit around it.

Connect with MCP

See the remote MCP authorization flow and available tools.

Use an SDK or the CLI

Build an owner-controlled integration with Darwin’s developer interfaces.

Embed Darwin in a product

Link each customer’s Darwin AI through a scoped Connect grant.