Get a setup proposal
Beta — behind the sonar-onboarding feature flag. Workspaces the flag is off for get 404 FEATURE_DISABLED.
The proposal the setup agent is building (or built) for a draft: status (proposing, measuring, sampling, then ready, needs_narrowing or failed), steps with timings, degraded (the degradation ladder’s codes — a degraded proposal is still complete), a timeline of stages and tool calls, and proposal once ready: keywords with volume ranges, reasons[] (rule, guide, measurement or judgement) and a plain explanation, scoping options, feeds, platforms and the whole-setup totals. 404 SETUP_PROPOSAL_NOT_FOUND when propose was never called for the draft.
Authorizations
Clerk API key. Create one in Settings → API Keys. Pass as Authorization: Bearer <key>. Keys carry a scope — read, write (implies read) or admin (implies write) — chosen when the key is minted. Each operation's security requirement (and its x-required-scope extension) names the minimum scope it needs; request the least-privileged key that covers the operations you call.
Path Parameters
The draft id (draft_…) the propose call returned.
1 - 64"draft_k3v9x0q2m1"
Response
200 response
The draft the proposal belongs to — also the {id} to poll.
proposing → measuring → sampling → proposing (the agent) → ready | needs_narrowing | failed. Poll until it is one of the last three.
scanning, scanned, proposing, measuring, sampling, ready, needs_narrowing, failed, applied The profile was edited after this proposal: propose again.
balanced, thorough Present once the status is ready or needs_narrowing.
