Write a request-response contract before asking AI to connect two systems. Define permitted data, authentication boundaries, failure behaviour, and success evidence using synthetic examples rather than credentials or private payloads.
Set the data-sharing boundary first
Cursor documents that AI features send prompts and code context to model providers. With Privacy Mode enabled, Cursor says code is not used for training by Cursor or other AI model providers. That stated restriction does not mean no data leaves the machine.
Cursor also describes Cloud Agents requiring repository access and temporarily storing encrypted repository copies while running, then deleting them after completion. As editorial advice, decide whether the proposed workflow and repository scope are appropriate before supplying integration context. Review privacy questions separately from API correctness.
Complete the request-response worksheet
Record these fields before generation:
- Operation: the precise business action, with read and write actions distinguished.
- Request: field names, types, required values, and rejected extras.
- Authentication boundary: which component supplies credentials, without including secret values.
- Success response: required fields and the evidence that the action completed.
- Error cases: invalid input, unauthorised request, missing record, timeout, and upstream failure.
- Retry rule: whether repetition is safe and how duplicates are recognised.
- Observability: which non-sensitive identifiers help trace a failed attempt.
If either system's verified contract is unavailable, label the missing details as unresolved. Do not let generated code turn a plausible guess into an assumed external API fact.
Hypothetical stock-check contract
Imagine a fictional stationery app checking availability from an internal demonstration service. The proposed request is {"sku":"DEMO-NB-01","quantity":3}; the proposed response is {"sku":"DEMO-NB-01","available":true,"availableQuantity":8}.
This is an invented review contract, not a real provider endpoint. Require quantity to be a positive integer and reject a request containing quantity -1. Define a separate unavailable response for a valid quantity exceeding stock. A timeout should remain “availability unknown,” not become “out of stock.”
Evaluate generated code against four synthetic fixtures: valid stock, insufficient stock, negative quantity, and timeout. Check whether the interface preserves those distinctions and whether logs avoid credentials or unnecessary payload content. Stock checking should not silently become stock reservation.
Stop when writes or retries are ambiguous
Pause integration if a retry could repeat an unintended write or if authentication responsibility is unclear. Next, obtain the missing system contract and review a minimal adapter before connecting additional operations.
If considering access options, check the coding catalog for access format and saved terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence or enterprise privacy arrangements.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Cursor privacy and data governance establishes the documented data flows and training restriction. The worksheet and stock payloads are hypothetical editorial guidance, not an API capability claim.