# Prism Crisis Radar API (https://www.socialcrawl.dev/platforms/prism/crisis-radar)

> Stage 1 computes a 7-day-rolling z-score on content_analysis daily phrase-trends (the breach gate, always 15 credits) and returns a calm\|watch\|alert\|crisis status. On a breach with confirm=true, Stage 2 fans out to sentiment + search/everywhere (items_by_source real counts) + reddit (sort=new) + twitter/ai-search (citations, not the chatty answer) + a triage anger-ordered search, then grades severity (+30 credits, charged only when a breach actually fires). A calm result or confirm=false costs only the 15cr baseline. The recurring alarm is delivered by wrapping this recipe in a monitor.

TL;DR: `GET /v1/prism/crisis-radar` costs 15 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `brand` | no | The brand to watch (required). |
| `sensitivity` | no | Z-score breach threshold (0.5-6, default 2.0). z>=sensitivity on volume or negative-share fires a breach. |
| `confirm` | no | true -> on a breach, run the escalation legs and grade severity (+30 credits, charged only when a breach fires). |
| `baseline_days` | no | Rolling-mean window for the z-score (3-30, default 7). |
| `date_to` | no | The day being evaluated (YYYY-MM-DD). Defaults to today. |

## Code example

```bash
curl "https://www.socialcrawl.dev/v1/prism/crisis-radar" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What is the SocialCrawl Crisis Radar API?

GET /v1/prism/crisis-radar runs a stateless breach check: stage one computes a 7-day-rolling z-score on a brand's daily mention volume and negative share and returns an alert_level of calm, watch, alert, or crisis. It is the run primitive a recurring crisis monitor wraps.

### How does the breach z-score work?

The endpoint pulls a daily phrase-trends series, computes the rolling mean and standard deviation over your baseline_days excluding today, and z-scores today against it. A breach fires when the volume or negative-share z crosses your sensitivity; fewer than three baseline days returns calm with a warning.

### Why is the level called alert_level and not status?

status is a reserved envelope key that the response transform strips, so the headline grade is returned as alert_level — one of calm, watch, alert, or crisis. The numeric z_volume, z_negative_share, and the full baseline_window are returned alongside it so the level is never status-only.

### What does confirm=true add and what does it cost?

Pricing is two-stage: the baseline check is a flat 10 credits. Pass confirm=true and, only when a breach actually fires, the endpoint fans out sentiment, universal search, Reddit, an X grok search, and a triage anger search to grade severity for an extra 30 credits — a calm result still costs only 10.

### Can I turn this into a recurring alarm?

Yes — that is the intended product. The computed block emits stable keys, an ISO window, and a methodology_version so the recipe wraps cleanly in a monitor that runs it on a schedule and pushes a webhook on a breach. The one-shot endpoint is the honest run primitive; the recurring alarm is the monitor.

See the full Prism API: https://www.socialcrawl.dev/platforms/prism

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- What API detects a spike in negative brand mentions?
- How do I run a z-score crisis breach check on brand mentions via API?
- best crisis detection API with a volume and sentiment z-score