---
title: "What data to ask for next, and what it would rule out"
method: POST
path: "/api/diagnose"
tags: ["marketing-feeds"]
---

# What data to ask for next, and what it would rule out

`POST /api/diagnose`

## Request

- Base URL: `https://peopleanalyst.com`
- URL: `https://peopleanalyst.com/api/diagnose`
- Auth: none declared

The acquisition planner. Given which data-stories are still candidates, returns the single most efficient next question, the full ranked list, and the minimum set of asks that makes every live story testable — split into what can be sent today versus what needs legal review. Ranked by information-per-friction: how evenly an answer splits the live hypothesis set (computed by entropy from the discrimination matrix, never hand-asserted) divided by a cost in which GOVERNANCE outweighs effort. Absent priors all live stories weigh equally, so results reflect structure, not likelihood. GET accepts ?live=, ?have=, ?lack= as comma lists.

## Query parameters

- `live` string
- `have` string
- `lack` string

## Response `200`

{ contract, caveat, live, nextAsk, ranked[], plan{ asks[], totalFriction, sendToday[], needsLegalOrCollection[] } }

- object

---

[API](https://skmtc.dev/peopleanalyst/apis/peopleanalyst-public-feeds.md) · [All operations](https://skmtc.dev/peopleanalyst/apis/peopleanalyst-public-feeds/llms.txt) · [OpenAPI document](https://skmtc.dev/peopleanalyst/apis/peopleanalyst-public-feeds/revisions/f369fadcfd61?raw)