Skip to main content
Darwin gives every account a personal agent and supports separate business agents for teams and organizations. Every supported surface resolves the same identity, permissions, conversations, tasks, wallet, approvals, skills, and connections.

​
Start building

  • Quickstart — Create an account, issue an API key, and make your first request.
  • Surfaces — Access the same agent from web, messaging, MCP, and the JavaScript SDK.
  • Agent — Understand identity, permissions, work, wallet, deployment, tools, and connections.
  • External applications — Add Sign in with Darwin, linked-agent grants, enrollment, wallets, and webhooks.
  • MCP — Connect Darwin to an MCP-compatible client.
  • API reference — Work directly with the HTTP API.

​
One account across every client

Darwin resolves every authenticated request to one accessible agent context. Name a personal or business agent naturally when you want to change contexts. Darwin keeps separate conversations and authority boundaries for each agent without requiring an agent identifier on every message.

​
Core principles

  • Owner scoped: API keys and agent actions belong to the authenticated Darwin user.
  • Intent routed: messages select the intended accessible agent from natural language and recent channel context.
  • Explicit authority: sensitive or irreversible actions create a request that needs attention.
  • Task oriented: /tasks is canonical across Buy, Sell, and Chat; private network and provider endpoints stay hidden.
  • Consistent: each agent’s conversation context is available across supported clients without mixing agent histories.