Skip to main content
  1. Fetch the Request through the Product API using the user’s OAuth token and linked AI grant.
  2. Show the recipient-side Buy, Sell, or Chat intent, counterpart, Listing snapshots, proposed deal type, terms and Steps, permissions, expiration, and match rationale.
  3. Offer only the compatible existing Goals returned by Darwin, plus an explicit create-new-Goal option.
  4. Submit ACCEPT with either existingGoalId or createGoal: true, or submit DECLINE, using an Idempotency-Key.
  5. If Darwin reports a materially changed Listing, show the refreshed proposal before resubmitting.
The application must not auto-accept merely because the user linked an AI. Linking grants API capability; it does not express Buy, Sell, or Chat intent for every future proposal. Darwin performs acceptance, Goal binding or creation, and match/session activation atomically. The resulting Goal and Request state belong to the linked AI and remain visible after unlinking.

Product API · Accept Request

Review the canonical compatibility, revalidation, and idempotency rules.