IntelligenceService

GetSimilarEvents

GetSimilarEvents returns historical precedents for a described situation. Same vector search as SearchIntelHistory over a longer free-text input, so it is likewise embeddings-backed and rate-policied. Premium-gated. PRO-gated. Requires entitlement tier >= 1.

post/api/intelligence/v1/get-similar-events

Request

  • Base URL: https://api.worldmonitor.app
  • URL: https://api.worldmonitor.app/api/intelligence/v1/get-similar-events
  • Auth: one of:
    • API key in header X-WorldMonitor-Key
    • API key in header X-Api-Key
    • HTTP bearer

Headers

Idempotency-Keystring

Optional client-generated idempotency key. Retrying a POST with the same key and an identical request body replays the original response (only the status, body, and Content-Type are reproduced) instead of re-executing; reusing the key with a different body is rejected with 422. For mutations this avoids duplicating the side effect, while for batch-read POSTs it replays a cached snapshot that can be up to 24 hours stale. Keys are scoped per authenticated caller (falling back to the source IP for unauthenticated endpoints) and retained for 24 hours.

Request body

situationstring required

Free-text description of the situation to find precedents for, e.g. "a naval blockade closes a major grain export corridor for weeks". Longer than a search query on purpose: more context ranks better.

domainstring

Restrict precedents to one producing domain. Empty searches every domain.

countrystring

Restrict precedents to one ISO 3166-1 alpha-2 country. Empty searches every country.

limitinteger

Maximum precedents to return. Defaults to 10 server-side when omitted or <= 0, capped at 32 by the handler.

Response

OK

situationstring

Echo of the situation text, so a caller multiplexing requests can pair a response back to its input.

partialboolean

True when a bounded candidate window may omit further precedents.

upstreamUnavailableboolean

True when the embedding provider or the history store could not be reached. The gateway reads this flag out of the body and switches the response to Cache-Control: no-store, so a transient outage is never pinned as a false-empty precedent list for the tier's full TTL.

Changes

No recorded changes to this operation across all 1 revision of this API.