Detect KOSA-aligned harm signals in text

The content to analyze

Top-level alias for options.support_threshold. Minimum severity to show crisis support resources (default: high). Critical always shows.

Opaque signed token from a previous /unsafe call. Carries derived analysis state — no message content is stored server-side.

Discard any continuation_token and start a fresh conversation.

Cross into a new conversation WITHOUT discarding the sustained_hopelessness pattern carried in continuation_token — unlike reset_conversation, which discards everything. Requires continuation_token to also be set. Use this when a new conversation starts on your side (e.g. a new chat session days later) but you still want Tuteliq to notice if the same pattern keeps recurring across those sessions.

Optional customer-side message id for evidence pointers.

Your unique identifier (e.g. message ID, content ID) for correlating Tuteliq results with your own system. Echoed back in the response and included in webhook payloads so you can match alerts to the original content.

Your end-customer identifier for multi-tenant / B2B2C scenarios. If you serve multiple customers (schools, apps, brands) from a single API key, set this to route webhook alerts to the correct customer. Echoed back in the response and included in webhook payloads as "customerId".

Per-call override of your account incident logging setting. When set, it takes precedence over the account-level flag for THIS request: true forces the incident to be persisted, false suppresses persistence. Omit to use your account default (which itself defaults to enabled). Lets you control incident logging per request, e.g. suppress logging for test traffic.

True when a declared context.conversation_type would have capped an urgent action to flag_for_review and did not, because the case is acute: the analysis named an acute marker, or a separate reading found a person at risk now with something happening as the text is written. A reading that gave no answer also keeps the urgency. Absent otherwise, and never present together with conversation_type_applied.

Human-readable explanation. Present only when urgency_kept is true.

Present only when a caller-declared context.conversation_type actually changed routing. Confirms the setting was taken into account, rather than leaving the platform to assume it was.

Unsafe-content signal observed at ANY severity (including low / monitor cases). For production branching prefer recommended_action (flag_for_review / block / immediate_intervention), which is a stable enum, over the bare presence of a signal. SCOPED TO THIS ENDPOINT: false means no KOSA-category signal was found HERE, not that the content is safe. It is also false where the sender is describing a harm rather than being subject to it. Peer harassment and image-based abuse of a named person are scored by /safety/bullying, so do not read false as a clearance without also calling that endpoint or /api/v1/analyse/multi.

Routing key, weakest to strongest: none, monitor, flag_for_review, block, immediate_intervention. Safe to switch on.

Optional human-readable expansion of recommended_action for a moderator UI. Free text: do not branch on it.

Language code used for analysis (auto-detected or provided)

Language support maturity: "stable" (en) or "beta" (all others)

Number of credits consumed by this request

Signed token carrying derived analysis state for the next call. Server stores nothing.

ISO 8601 expiry timestamp of the continuation_token.

How prior state was sourced.

Conversation-level risk 0-1, distinct from risk_score which scores only this message. Anchored on the highest severity seen so far and decaying slowly across benign turns. Absent on the first turn. Derived from the signed token: no message content is stored to produce it.

Direction of travel across the conversation so far.

Count of distinct conversations, within the last 30 days, that named the hopelessness_sustained marker at least once. Only present when new_conversation has been used to cross at least one conversation boundary. recommended_action is floored to at least flag_for_review once this reaches 3.

True when a critical-severity coded-term match corroborated this detection but the model's own independent read wasn't itself concerned enough to also corroborate escalation to immediate_intervention. Absent when no cap applied.

Human-readable explanation of the cap. Present only when escalation_capped is true.

True when this detection rests on a child reporting, disclosing or reacting to a real risk involving somebody, rather than on anyone in the conversation enacting one -- a peer saying another child has self-harm marks, that a sibling is using again, that a suicide challenge is going round. Route these to a welfare/safeguarding queue rather than an intervention queue: the speaker is the person who spoke up, and the risk may belong to somebody who is not in the conversation. Set only when the verdict rests on that report: if the analysis independently called the content unsafe, this is absent and recommended_action carries the answer. This path itself raises neither severity nor action, but it is NOT a cap on the response -- always route on recommended_action, which can be anything up to immediate_intervention. Absent unless it applied.

Human-readable explanation. Present only when third_party_concern is true.

True when the caller declared an adult age group but the speaker states a minor age in the message or in the earlier turns sent with it. The declared age was not used. Nothing is escalated by this on its own; the analysis runs as if no age had been sent. Worth investigating at your end: an age check that disagrees with what the user says is what a bypassed age verification looks like. A stated ADULT age never has this effect. Absent unless it applied.

Human-readable explanation. Present only when declared_age_overridden is true.

True when an alert was lowered because a separate reading found a text working against the harm it describes: teaching, moderating, counselling, reporting or asking for advice. Two outcomes. When nobody is at risk in the text and the speaker is describing someone else, nothing is detected and the action is monitor. When a person is at risk and a responsible adult in the text is already acting, an urgent action becomes flag_for_review with the severity and score brought down, and never lower. It never applies to a person speaking about their own risk, to a verdict supported by an acute marker, or when earlier turns are in play. Absent unless it applied.

Human-readable explanation, naming which of the two outcomes applied. Present only when protective_speech_capped is true.

True when an alert rested on a number that is also known as a code, and a separate reading found the number in ordinary use (an address, a count, a price, a room) with nothing else harmful in the content. The verdict was cleared. Absent when this did not happen.

Human-readable explanation. Present only when number_coincidence_cleared is true.

True when a review alert whose ONLY concern was low mood was lowered to monitor because a separate reading found the words were not meant literally: an exaggeration or an everyday expression about a task, a person or an event ("I can't take this homework any more"), a quotation, or something past and resolved. It applies only when the detector named low mood and nothing else, with no acute marker and no earlier turns in play; self-harm, a threat or any other category and it is never asked. The categories, severity and score are unchanged. It never clears to none. Absent unless it applied.

Human-readable explanation. Present only when figurative_low_mood_capped is true.

True when an alert that a rule for declared minors had raised was lowered ONE step because the text is banter between people who know each other: every strong word is an exaggeration about an everyday frustration (homework, a chore, a game), the other person answers in kind, nobody asks for it to stop or shows fear or hurt, nothing is kept from an adult beyond the trivial matter itself, and nobody says how they feel about themselves or their life. A raise to flag_for_review is lowered to monitor, with unsafe false. A raise to immediate_intervention is lowered to flag_for_review and no further, with everything else in the result unchanged, so a person still looks. It applies only when the analysis named no acute marker, its own action was lower than the one returned, and two separate readings agree; any other answer, or no answer, keeps the alert. banter_capped_reason says which step was taken. Absent when it did not apply.

Human-readable explanation. Present only when banter_capped is true.

True when the request declared no age group and a review alert was lowered to monitor because nothing in the message shows a child. It applies only when every category named is one that ordinary adult life is mistaken for (sexual content, risky behaviour, substance use), with no acute marker and no earlier turns in play, and a separate reading found the writer mentioning their own everyday life, with no sign of anyone under 18 and nobody hurt, pressured or in danger. A declared age group, a message about another person, or any other category, and it is never applied. The categories, severity and score are unchanged. It never clears to none. Absent unless it applied.

Human-readable explanation. Present only when no_child_shown_capped is true.

True when earlier turns were submitted, the analysis found nothing in the latest message, and a separate reading of the whole conversation found that someone expressed distress about their own life in an earlier turn (surfaced as distress_context at monitor) or said something about ending their life or hurting themselves (surfaced as self_harm for review). Only ever surfaces; never lowers a result. Absent otherwise.

Human-readable explanation. Present only when conversation_distress_surfaced is true.

True when the only concern named was that a location or an arrangement was given (an address, a place, a time), no acute marker was present, and a separate reading found practical detail for an ordinary purpose and nothing else in the message. A location is not unsafe on its own, so the verdict is cleared (unsafe false, recommended_action none). Absent when it did not apply.

Human-readable explanation. Present only when logistics_only_capped is true.

Echo of the external_id you provided in the request

Echo of the customer_id you provided in the request