# Prism (/docs/prism)



Prism [#prism]

Prism endpoints are **composites**. One call fans out to several platforms in parallel, merges the results, and returns a single computed answer, so you don't orchestrate the fan-out, the retries, or the merge yourself.

Base URL: `/v1/prism/...`

<Callout>
  Every number a Prism composite returns is 

  **computed in code, not generated by a model**

  . Where a composite does use an LLM (topic clustering, tone labels), it narrates data that was already computed deterministically.
</Callout>

How do I get started with Prism? [#how-do-i-get-started-with-prism]

1\. Pick a composite by the question you're answering [#1-pick-a-composite-by-the-question-youre-answering]

Each composite answers one question end to end. `handle-audit` answers "is this handle worth pulling"; `comments` answers "what did everyone say on this post"; `reputation` answers "how is this brand seen across review sites".

2\. Make the call [#2-make-the-call]

```bash
curl "https://www.socialcrawl.dev/v1/prism/handle-audit?handle=mrbeast" \
  -H "x-api-key: sc_your_api_key_here"
```

3\. Read the coverage block [#3-read-the-coverage-block]

A composite is a fan-out, so a leg can fail without failing your call. Responses carry a coverage signal (`legs[]`, `sources_succeeded`, `coverage`, or a `confidence` block depending on the composite) telling you which sources answered. Billing differs by composite. For `handle-audit`, every successful HTTP 200 receives the full request-shaped charge, even with partial evidence; there is no partial refund.

4\. Read computed fields [#4-read-computed-fields]

Each composite returns fields tailored to its question. `handle-audit` returns score-v2 evidence, nullable scores, component coverage, surface estimates, and leg diagnostics. Direct post and author endpoints may include shared computed fields such as `engagement_rate`, `language`, and `content_category`; see [Computed fields](/docs/computed-fields) for formulas and null semantics.

What Prism composites can I access? [#what-prism-composites-can-i-access]

<PlatformEndpoints platform="prism" />

<Callout>
  Some cross-platform composites live outside the 

  `/v1/prism/...`

   namespace because they belong to a single source's vocabulary — for example 

  `/v1/search/everywhere`

  , 

  `/v1/search/forums`

  , 

  `/v1/reddit/omni-search`

  , 

  `/v1/naver/brief`

  , and the per-platform 

  `/v1/{platform}/profile/full`

  . Browse them all on the 

  [Prism overview](/prism)

  .
</Callout>

How is Prism priced? [#how-is-prism-priced]

Composites are priced per call, not per leg, and the price is listed on each endpoint's reference page. Three shapes exist:

* **Flat** — one price per call regardless of how many legs run (for example `prism/reputation`).
* **Param-derived** — the price is fixed by the request shape, so you know it before you call (for example `prism/handle-audit` is 5 credits for up to 4 platforms, +1 per extra).
* **Metered** — a ceiling is held upfront and the unused portion is refunded, because the work depends on what the data turns out to be (for example `prism/comments`, billed per comment page).

For `handle-audit`, a public response-cache hit costs 0 credits. A non-200 execution failure after deduction receives a full refund; request-validation errors happen before billing.

If every leg fails, the whole call is refunded. See [Endpoint pricing](/docs/endpoint-pricing) for the full table.

What should I know about Prism data? [#what-should-i-know-about-prism-data]

* Composites use `GET` with query parameters, except the bulk endpoints (`prism/post-stats`, `prism/profiles`, `prism/comment-lookup`), which take a `POST` JSON body.
* Authentication via the `x-api-key` header.
* Responses follow the unified SocialCrawl schema, so a profile returned by a composite is byte-identical to the same profile from its native endpoint.
* Long-running composites can stream Server-Sent Events when you send `Accept: text/event-stream`, emitting each leg as it settles.