Introduction

SigWise reads the events and messages on your platform and answers the questions you configure about each object (a user, a listing, an order) as typed signals.

          POST events / messages                 GET answers
your app ───────────────────────►  SigWise  ◄────────────────── your app
                                     │  ▲
                            schedule │  │ store answers
                                     ▼  │
                               analysis queue ──► analyzer (LLM)
                                     │
                                     └──► webhooks, rules (Slack, email, webhook)

1. Configure signals. Say what you want to know: is this a scammer?, how trustworthy is this user?, what is their buyer intent? A signal is an API call away, and every new account starts with those three.
2. Send events. Post what happens on your platform: profile edits, logins, messages between users. Ingestion returns 202 right away.
3. Read the answers. Analysis runs in the background, debounced so a burst of events produces one analysis. Read the latest answers, search objects by them, or have them pushed to you.

What you get back

Each signal is one of three types, and its answer is typed accordingly:

Type	Answer	Example
noul	a probability between 0 and 1	is this a scammer?
score	a position on a labelled spectrum	trust score
choice	one option out of N, with probabilities	buyer intent

{
  "object_id": "user-42",
  "event_count": 7,
  "analysis": [
    { "key": "is_scammer", "type": "noul", "noul": 0.91, "model": "model-1", "computed_at": "2026-09-27T10:00:05Z" },
    { "key": "trust_score", "type": "score", "score": 0.4, "confidence": 0.8, "model": "model-1", "computed_at": "2026-09-27T10:00:05Z" }
  ],
  "pending": []
}

Ways to use it

• Background scoring. Send events as they happen and read answers when you need them, such as on a moderation dashboard or before a payout.
• Direct moderation. Send "wait": true to score a message inline and block it before other users see it. See Direct moderation.
• Automation. Get a signed webhook for every completed analysis, or define rules that alert Slack or email when, say, is_scammer >= 90.

Next steps

• Quickstart: your first signal, event and answer in five minutes.
• Authentication: how requests are signed.
• API reference: every endpoint and schema.