prism

The real questions a topic's audience asks: harvested from Reddit + YouTube threads (Naver KnowledgeiN for Korean topics) and clustered by intent (who/what/why/how/vs).

Searches Reddit and YouTube (and optionally the universal web search) for a topic, picks the titles and comments that ask a real question (a judgment per text, so Korean and other questions without a "?" count; methodology.question_detection reports how they were picked, with a punctuation heuristic as the fallback), and LLM-clusters them into labeled intent groups with verbatim quotes and per-question source counts (the model only labels/groups: counts and quotes are recomputed in code). The clustering degrades to one ungrouped cluster on LLM failure (no refund). Coverage spine = the per-source search legs (<0.5 → 50% refund; all dead → full refund). Great for content/SEO briefs and FAQ generation. Korean topics: naver adds Naver KnowledgeiN, Korea's question site, as one search of up to 100 rows; every KnowledgeiN row is a question someone asked, so it is kept without judging and counted once per question (KnowledgeiN lists one row per answer), and its raw rows are under sources.naver. A topic written in Hangul defaults to naver,youtube, because Reddit's search returns unrelated threads for Korean terms; pass platforms= to choose for yourself.

get/prism/audience-questions

Request

Base URL: https://www.socialcrawl.dev/v1
URL: https://www.socialcrawl.dev/v1/prism/audience-questions
Auth: API key in header x-api-key

Query parameters

topicstring required

The topic/keyword to mine audience questions for.

platformsstring

CSV subset of reddit,youtube,web,naver. Default reddit,youtube; a topic written in Hangul defaults to naver,youtube (naver = Naver KnowledgeiN questions).

max_questionsinteger

Cap on questions returned.

threads_per_sourceinteger

How many top threads to dig per source.

timeframestring

Recency window.

includestring

Set web to add the universal-search leg.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "prism",
  "endpoint": "/v1/prism/audience-questions",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.