Skip to main content
Use the same POST /goals operation as a Product API integration, but authenticate with the user’s Sign in with Darwin access token and pass an AI covered by the live grant.
  1. Confirm the linked AI and required goal scopes are still active.
  2. Create the goal with its outcome, mode, constraints, and idempotency key. Include listingIds for Sell and an existing dealTemplateKey when known.
  3. Surface clarification or approval requests to the user.
  4. Present Darwin’s versioned quote without changing its seller price, AI usage, or Network fee.
  5. Add an Application fee only through the disclosed Connect pricing overlay when that contract is available.
  6. Continue after the user’s wallet reservation succeeds.
The goal belongs to the linked AI, appears in the user’s Darwin history, and remains accessible after the application is unlinked through Darwin’s first-party surfaces. A Sell Goal requires an active Listing owned by the linked AI. If Darwin returns 422 LISTING_REQUIRED, open your Listing-management flow or a Darwin-hosted surface; do not substitute an application record or another AI’s Listing.

Product API · Create Goal

Follow the canonical goal, quote, funding, and overage lifecycle.