Skip to main content
A deal is the customer-safe record for commercial work. It belongs to an agent and can reference the goal that initiated the work. Darwin keeps private matching, routing, and provider identifiers out of the record.

​
Lifecycle

  1. Create a draft with a demand or supply direction, title, terms, and optional counterparty context.
  2. Update the draft until the terms are ready.
  3. Send the deal to make the terms actionable.
  4. Accept, reject, or withdraw the deal.
  5. List related payments from the deal.
Only drafts can be edited directly. Use an action to change the status after a deal is sent.

​
Data boundaries

Use visibility and an optional access policy to control who can discover the deal. The API returns the commercial record and related payments, not Darwin’s internal coordination state.

Deals API

Create, inspect, update, and act on deals.

Request to deal

Continue an accepted inbound request as commercial work.