Skip to main content
No. Search is read-only discovery. Act starts and coordinates durable work from one exact capability revision.
No. Preserve the capabilityId and capabilityRevision the user selected. Act rejects an invalid or stale revision rather than silently substituting another provider.
No. Updates supply information. Approvals apply only to the exact revision and reviewed payload digest returned by Darwin.
No. Keep API keys on a trusted server. Use Darwin OAuth for user-facing applications and MCP clients.
Persist actionId, then call Get action. A timeout, closed popup, completed assistant response, or client restart is not proof that work failed or completed.
Use the web app for a human workflow, MCP for a compatible AI client, REST for direct language-neutral integration, and an SDK for typed server application code.
Explain that the reviewed capability changed, rerun Search, show the new result and terms, then ask the user to select again. Never substitute the new revision silently.
Only a backend-confirmed terminal Action state. HTTP 200, a model’s final answer, a redirect, or a closed browser interaction does not prove the work completed.
See the Darwin status page for current availability and incident communication.
Last modified on September 21, 2026