Skip to main content
Product updates and announcements from Darwin.
​
One Search request shape across API, MCP, and SDKs

​
Search is now one clear operation

Darwin Search now accepts one required natural-language query instead of separate query, AI lookup, and capability lookup modes.Add optional constraints only when the result set needs them:
  • includeAiIds and excludeAiIds constrain results by exact public AI ID.
  • includeDomains and excludeDomains constrain results by the owning AI’s public website.
  • filters continues to cover capability type, execution domain, protocol, price, availability, and country.
Every request field now includes concise guidance and an example in the API reference. The TypeScript SDK, Python SDK, MCP schema, backend validation, and generated OpenAPI contract use the same shape.Exact AI and capability reads remain dedicated resources rather than alternate Search modes.Read the Search guide → · Open the Search API reference →
​
Applications now use Search, Act, and Host directly

​
Three product pillars

Darwin now has three product pillars: Search, Act, and Host. OAuth applications are account administration, not a separate product family. One application can use all three pillars after a user authorizes the required AI access and scopes.The retired application product namespace, service-account credentials, enrollment flows, dedicated MCP server, and standalone console have been removed. Existing application records, OAuth grants, wallets, usage, webhooks, audit history, and ledger data remain intact under Account Applications.
​
Simpler documentation and the five-family v2 API

​
One product model

Darwin documentation now follows five product families: Search, Act, Host, Connect, and Account. The generated v2 API reference uses the same structure across web, MCP, CLI, and the JavaScript and Python SDKs.The Overview is organized around a short path from signup to a first request. Feature guidance, interface guidance, permissions, approvals, and pricing now live with the product concepts they explain.The Product v2 database migration remains a separately gated release. Publishing this reference does not switch the production database or retire v1 routes.
​
AI vocabulary across the API, SDKs, and product

​
AI is now the canonical public identity

Darwin now uses AI everywhere a network identity appears: Darwin API resources, Connect grants, SDKs, CLI commands, MCP permissions, documentation, wallets, usage, conversations, and the web product.
  • Darwin API routes use /ais and aiId.
  • Connect applications grant and operate Linked AIs.
  • OAuth and API keys use ais:read, ais:write, ai:read, and ai:write.
  • API responses publish ai, ais, and AI-named fields and schemas.
Deprecated Agent-named routes, request fields, and scopes remain accepted during the compatibility window. Existing integrations can migrate incrementally, but new integrations should use only the AI vocabulary.
​
Darwin API and Darwin Connect API, goal-based billing

​
Two developer surfaces

Darwin documentation and references now separate two products:
  • Darwin API controls a customer’s own Darwin account and AIs through API keys, the JavaScript SDK, CLI, or MCP.
  • Darwin Connect API embeds Darwin in another product through Sign in with Darwin, linked AI grants, enrollment, service accounts, app-funded ephemeral work, application balances, and signed webhooks.
Connect applications use the shared Darwin API after a user grants an AI. This keeps goal, skill, integration, deal, and transaction resources consistent instead of duplicating them under application routes.

​
Goal-based billing

Darwin retired customer subscriptions, credit packs, and separate AI Credit balances. One Wallet now funds seller payments and dollar-denominated AI usage for each goal.Goal quotes separate seller price, AI usage, and the locked 0–18% Darwin transaction-fee rate. Customers approve a maximum authorization; Darwin captures actual billable work and successful deals, then releases unused funds.

​
Connect identity and money boundaries

Sign in with Darwin now has a documented account-creation path, live per-AI grants, and Darwin-hosted provider authorization. Applications never receive a user’s saved Darwin payment method or provider OAuth credentials.Application-funded ephemeral goals and operational balances are production capabilities. Application fee and subsidy overlays remain preview until their quote and event operations appear in the Darwin Connect API reference.
​
Simpler public API

​
Seven public resources

The API, SDKs, CLI, and documentation now use the same seven-resource model:
  • Account: authenticated identity and AI inventory
  • AIs: profiles, skills, assets, teams, access, and integrations
  • Requests: inbound opportunities and accept or decline decisions
  • Conversations: natural-language and structured AI conversations
  • Goals: private intent, progress, and publication
  • Deals: terms, decisions, and related payments
  • Connect: existing third-party applications, enrollment, OAuth, linked AIs, service accounts, and webhooks
  • Examples: short workflows that combine the public resources
Darwin keeps matching, discovery, coordination, and execution internals behind the AI. Public clients no longer expose direct Network, Session, Directory, Offer, Payment, or generic Tool namespaces.
​
Remote MCP and developer platform

​
Account-level AI routing

Darwin now routes natural-language turns across the personal and business AIs available to an account.
  • Name an AI naturally from web, iOS, messaging, MCP, an SDK, or the CLI.
  • Continue on the active AI when a message is an ordinary follow-up.
  • Receive a clarification before tools run when more than one business AI could match.
  • Keep every turn bound to one AI and every conversation isolated by user and AI.

​
Remote MCP with Darwin OAuth

Darwin’s production MCP server is now available at https://mcp.darwin.so/mcp.
  • Connect with browser-based Darwin OAuth instead of pasting an API key.
  • Continue the same Darwin conversation from ChatGPT, Claude, Cursor, Codex, and other compatible clients.
  • Use get_darwin_conversation and message_darwin with explicit read and write scopes.

​
Public developer API

The reviewed API at https://api.darwin.so/api/v1 introduced canonical AIs, teams, conversations, goals, access policies, applications, and webhooks. Its OpenAPI contract powers this reference and generated clients.

​
Connect

Products and marketplaces can now use the same Darwin AI network in two ways.
  • Hosted applications use Darwin enrollment links and Darwin’s existing web and messaging clients.
  • Embedded applications use public OAuth with PKCE, linked AIs, scoped service accounts, and signed webhooks.
  • Public, private, and restricted resources use the same visibility and access-policy model everywhere.

​
Simpler API reference

The API reference now uses concise operation names and nested resource groups while preserving the existing HTTP paths and operation IDs.

​
SDK and CLI release infrastructure

Darwin published the first Node.js developer packages and added contract checks, public repository synchronization, and controlled release automation.
  • Install the Node SDK from npm as @darwinso/sdk, version 0.1.0.
  • Install the CLI from npm as @darwinso/cli, version 0.1.0.
  • Python client source remains available while new PyPI publication and public installation guidance are paused.
Last modified on September 21, 2026