INDICATORS REFERENCE

Information Warfare Indicators

Information Warfare covers 4 indicators across 2 signal groups. Each signal has a stable slug and code for programmatic access. Representative signals are shown publicly; the complete reference is available to customers.

Published signal families only. The full operational taxonomy is provided under a signed access agreement.

Features

Indicators

Signal Groups

Avg / Group

Overview Signal Groups Indicators Features

2 results

Showing 2 representative indicators of 4. The complete taxonomy is available to customers.

Request access

#	Indicator	Slug	code	Signal Group
001	synchronized messaging	`synchronized_messaging`	`coordination_indicators.synchronized_messaging`	Coordination Indicators
002	inauthentic amplification	`inauthentic_amplification`	`astroturfing_indicators.inauthentic_amplification`	Astroturfing Indicators

Browse by Signal Group

Alternatively, explore indicators grouped by their parent signal group:

Coordination Indicators

coordination_indicators

2 Indicators

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

Astroturfing Indicators

astroturfing_indicators

2 Indicators

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

Reading Information Warfare output

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

Intended task

Surface documented coordination patterns - synchronized messaging, template reuse, inauthentic amplification - across multilingual text streams, under access agreement.

Input requirements

text - the only field analyzed; up to 4,096 Unicode code points.
Deployment-specific languages and access - coverage is scoped per agreement, not self-serve.
No context beyond text - no user IDs, history, profiles, or attachments are read or inferred.
Deployed under custom agreements - coverage, inputs, and signal families are scoped per engagement.

Ordinary positive

“As a local resident I am shocked nobody is talking about the plant closure - share if you agree.”

platform_coordination high

coordinated_inauthentic_behavior medium

Safe inference: The post uses documented first-person-local and amplification-bait patterns - a lead worth correlating with sibling posts, not a verdict.

Confusing negative · Look-alike

“A genuinely viral meme repeated near-verbatim by thousands of unrelated users.”

What happens: Organic amplification can resemble coordination: signals flag coordination-shaped language and repetition patterns, which real viral content also produces.

Why it's tricky: Coordination signals are investigative leads under agreement - correlation across sources, timing, and accounts is what separates a campaign from a meme, and that correlation happens in your analysis, not in a single signal.

What you can safely infer

Which published signal families the text matched.
That matched patterns are documented and replayable under the deployed configuration.

What you must not infer

✕Attribution to a state or actor - signals are not attribution.
✕That organic content is coordinated, or that coordinated content is organic - signals flag patterns, analysts decide.
✕That an unmatched stream is clean - the published families are a subset of what a deployment covers.

Boundary: Coordination signals are investigative leads - they are not attribution. A matched pattern means the text resembles documented coordination tactics; it does not establish who is behind it or whether a campaign exists.

Signal reference 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 Information Warfare Docs View Signal 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 4 indicators

Benchmark Methodology

How we measure Top-3 Hit Rate

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