We are currently building something exciting and will be launching soon. Registration is temporarily closed. Launching soon — registration temporarily closed.

INDICATORS REFERENCE

Crisis Intelligence Indicators

Crisis Intelligence covers 650 indicators across 7 analysis groups. Each signal has a stable slug and code for programmatic access. Representative signals are shown publicly; the complete reference is available to customers.

View Analysis Groups Features

650

Indicators

7

Analysis Groups

21

Languages

93

Avg / Group

Overview Analysis Groups Indicators Features

7 results

Showing 7 representative indicators of 650. The complete taxonomy is available to customers.

Request access

#	Indicator	Slug	code	Analysis Group
001	action	`action`	`action_coordination.action`	Action Coordination
002	accountability	`accountability`	`identity_emotion.accountability`	Identity Emotion
003	accelerator	`accelerator`	`info_dynamics.accelerator`	Info Dynamics
004	abuse	`abuse`	`humanitarian_migration.abuse`	Humanitarian Migration
005	agreement	`agreement`	`governance.agreement`	Governance
006	access	`access`	`threat_conflict.access`	Threat Conflict
007	ad hominem	`ad_hominem`	`influence_ops.ad_hominem`	Influence Ops

Browse by Analysis Group

Alternatively, explore indicators grouped by their parent analysis group:

1

Action Coordination

action_coordination

73 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

2

Identity Emotion

identity_emotion

107 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

3

Info Dynamics

info_dynamics

97 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

4

Humanitarian Migration

humanitarian_migration

83 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

5

Governance

governance

90 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

6

Threat Conflict

threat_conflict

116 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

7

Influence Ops

influence_ops

84 Indicators

The complete signal list for this analysis group is available to customers. Request access to view it.

Reading Crisis Intelligence output

What you can safely infer from a result - and what you must not.

Intended task

Classify crisis-related text - field reports, news copy, public posts - into documented analysis groups covering displacement, humanitarian need, governance, and information dynamics.

Input requirements

text - the only field analyzed; up to 4,096 Unicode code points. Over the limit is rejected with input_too_long, never truncated.
language - must be a language this analyzer supports. Unsupported codes are rejected with 400 unsupported_language, never analyzed as a different language.
analyzers - include "crisis-intelligence"; up to 2 analyzers per request, one billed run each.
No context beyond text - no user IDs, history, profiles, or attachments are read or inferred.
Single texts, not streams - correlation across sources is your pipeline's job.

Ordinary positive

“Roughly 400 families crossed the border overnight after shelling cut the bridge; the reception camp has run out of tents.”

migration_border very high

humanitarian_vulnerability high

Safe inference: The text describes displacement and humanitarian need in the documented language of those categories. Route it to the monitoring desk for that region.

Confusing negative · Reported speech

“Officials claimed 400 families crossed the border overnight, but journalists at the crossing reported no movement and no new arrivals.”

What happens: Migration and displacement signals can still fire: the text describes the event in the documented vocabulary even though it disputes it. The analyzer reads language - it does not adjudicate whether the event happened.

Why it's tricky: Text describing an event is not verification that the event occurred. Denials, debunks, and contested claims can match the same categories as genuine reports - use signals to triage reading volume, then verify through your sources.

What you can safely infer

Which documented analysis groups and indicators the text matched.
That a high band means the text strongly matches the documented language of the category - useful for triage order.

What you must not infer

✕That the described event is verified, current, or correctly attributed.
✕Casualty or displacement figures as facts - they are claims made in the text.
✕That absent signals mean no crisis - coverage depends on the documented taxonomy and the language of the report.

Boundary: Signals describe text, not events. A displacement or conflict signal means the text uses the documented language of that event type - it is not independent verification that the event occurred, and it carries no validation of figures, dates, or attribution.

Signal reference Evaluation evidence Understanding signals API reference Evaluate on your data

Using Indicators in API Responses

When you call /v1/analyze, the response includes matched indicators with signal-match scores. Each signal is identified by its code and includes a level field (“category” or “label”). A score expresses signal-match strength under a particular analyzer configuration. It is not a probability that the signal or a downstream action is correct. Validate action thresholds on representative labeled data.

{
    "language": "en",
    "language_source": "declared",
    "signals": [
        {
            "analyzer": "trust-safety",
            "code": "insults_derogation",
            "label": "Insults & Derogation",
            "score": 0.86,
            "level": "category"
        },
        {
            "analyzer": "trust-safety",
            "code": "insult",
            "label": "Insult",
            "score": 0.99,
            "level": "label",
            "parent": "insults_derogation"
        },
        {
            "analyzer": "trust-safety",
            "code": "belittling",
            "label": "Belittling",
            "score": 0.99,
            "level": "label",
            "parent": "insults_derogation"
        }
    ],
    "meta": {
        "analyzers": [
            {
                "name": "trust-safety",
                "status": "completed",
                "applicability": "analyzable",
                "assessment": "signals_detected",
                "signal_count": 3,
                "billed": true
            }
        ]
    },
    "usage": {
        "analyzer_runs": 1,
        "billed": true
    },
    "verification": {
        "version": 3,
        "configuration": "sqcfg_ZZW77NM9",
        "fingerprint": "fp2_8a72c4...19f",
        "input_commitment": "ic3_31bd5e...a42",
        "signature": "sig_ed25519_4c1f...e2a",
        "key_id": "edk_af4f218e",
        "binding_key_id": "bk_31bd5e42f7a019c8"
    }
}

Back to Crisis Intelligence Docs View Analysis Groups

Quickstart Guide

First API call in under 5 minutes

API Reference

Full endpoint documentation

Benchmark Results

Per-language Top-3 Hit Rate

Pricing

From Free to Enterprise

Playground

Test detection live - no API key

Indicator Dictionary

Browse all 650 indicators

Benchmark Methodology

How we measure Top-3 Hit Rate

Request access5,000 analyzer runs/month · No card required