ANALYSIS GROUPS REFERENCE
Crisis Intelligence Analysis Groups
Crisis Intelligence organizes detection into 7 analysis groups covering 650 indicators across 21 languages.
All Analysis Groups
Each analysis group contains a set of specific indicators that the API can detect. Click a group to expand its signal list. Signal lists are available to customers - sign in to view them.
01
Action Coordination
action_coordination
73
73 signals - request access
for the complete list.
View 73 indicators
Action Coordination
action_coordination
The complete signal list is available to customers. Request access to view it.
02
Identity Emotion
identity_emotion
107
107 signals - request access
for the complete list.
View 107 indicators
Identity Emotion
identity_emotion
The complete signal list is available to customers. Request access to view it.
03
Info Dynamics
info_dynamics
97
97 signals - request access
for the complete list.
View 97 indicators
Info Dynamics
info_dynamics
The complete signal list is available to customers. Request access to view it.
04
Humanitarian Migration
humanitarian_migration
83
83 signals - request access
for the complete list.
View 83 indicators
Humanitarian Migration
humanitarian_migration
The complete signal list is available to customers. Request access to view it.
05
Governance
governance
90
90 signals - request access
for the complete list.
View 90 indicators
Governance
governance
The complete signal list is available to customers. Request access to view it.
06
Threat Conflict
threat_conflict
116
116 signals - request access
for the complete list.
View 116 indicators
Threat Conflict
threat_conflict
The complete signal list is available to customers. Request access to view it.
07
Influence Ops
influence_ops
84
84 signals - request access
for the complete list.
View 84 indicators
Influence Ops
influence_ops
The complete signal list 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 withinput_too_long, never truncated.language- must be a language this analyzer supports. Unsupported codes are rejected with400 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.”
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.
Access the taxonomy through the API
Check Crisis Intelligence availability and endpoint programmatically via the public catalog endpoint - no authentication required. Include your API key to also retrieve taxonomy size and supported languages.
curl -X GET https://sentiqra.tech/v1/meta/domains/crisis-intelligence \
-H "Authorization: Bearer sq_live_your_key_here"
Example response (authenticated):
{
"catalog_version": "...",
"domain": {
"id": "crisis_intelligence",
"name": "Crisis Intelligence",
"status": "production",
"taxonomy": { "groups": 7, "detection_labels": 650 },
"languages": [ ... ]
}
}
Signals returned by the analyzers use code for the category or label slug - these correspond to the categories and indicators documented on this page.