Detect weak security signals API

Identify early suspicious-activity indicators from caller-supplied events. Weak signals are hypotheses with explicit confidence—not confirmed attacks.

The Detect weak security signals operation is part of the Security Signal Intelligence API on BRAINIAC.software. Identify early suspicious-activity indicators from caller-supplied events. Weak signals are hypotheses with explicit confidence—not confirmed attacks. It is exposed as POST /api/v1/security-signals/weak-signal-detect and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied security events and supported log/JSON/CSV exports processed locally Limitations: The caller's network and security infrastructure are not accessed. Observed facts are separated from inferred threat hypotheses. Events are not labeled confirmed attacks without sufficient multi-signal evidence. Detections are local rule and time-window analyses over supplied records. Missing values are not invented. No paid threat-intel feed or endpoint agent is used and no API key is required. Severity scores are explainable rule weights, not vendor risk scores. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Correlate security events, Detect attack sequences, Detect insider-threat signals, Detect privilege-escalation indicators. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/security-signals/weak-signal-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/security-signals/weak-signal-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-04T21:00:00.000Z",
  "events": [
    {
      "id": "E1",
      "at": "2026-11-04T20:00:00.000Z",
      "eventType": "auth_failure",
      "category": "auth",
      "userId": "u1",
      "host": "vpn-1",
      "outcome": "failure",
      "labels": [
        "first_seen"
      ],
      "source": "Caller-supplied"
    },
    {
      "id": "E2",
      "at": "2026-11-04T20:02:00.000Z",
      "eventType": "recon",
      "userId": "u1",
      "host": "vpn-1",
      "message": "port scan probe",
      "source": "Caller-supplied"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Security Signal Intelligence APIFull docsHow it works