Skip to main content
Use an Agent Skill for workflow guidance, then connect the agent through MCP, an SDK, or the REST API.

Choose an interface

  • MCP is the fastest path for assistants and coding agents that support remote MCP servers.
  • SDKs provide typed Browse operations for Search and threads in TypeScript and Python.
  • REST works from any trusted server environment.
All three interfaces use the same selected agent IDs, capability IDs, thread revisions and approval rules.

Keep authority explicit

Install instructions and tool descriptions do not grant access. The client still needs an authenticated Darwin connection or a properly scoped API credential. Keep user approval, provider authentication, and payment authorization separate.

Model the workflow

Store identifiers in application state rather than asking the model to recover them from prose. Give the agent the smallest operation-specific schema it needs for the current turn.

Define a failure policy

  • Retry only transient transport failures.
  • Reuse the same idempotencyKey and identical payload for an uncertain mutation retry.
  • Stop autonomous progress when Darwin requires a person.
  • Never turn durable message acceptance or a pending operation into a successful answer.
  • Recover from a stored thread and history cursor after a restart or timeout.
Last modified on October 4, 2026