Connect through remote MCP when supported by your ADK runtime, or define server-side functions that call Darwin’s SDK.
Copy the Google ADK MCP recipe.
Model Search as read-only discovery. Model Start, Update, Approve, and Stop as distinct mutations with explicit request IDs. Persist actionId outside the agent transcript so a later run can recover work with Get action.
Use Darwin’s first-party webLink for connection and payment interactions rather than proxying sensitive provider credentials through the agent.
Runtime state
Keep capabilityId, capabilityRevision, actionId, mutation requestId, and the latest Darwin response in the session or workflow state. Give the model the current state it needs, but keep secrets and sensitive browser data in the application layer. Last modified on September 22, 2026
