Skip to main content
Each recipe below is a working integration, not a sketch. Set EXORDE_API_KEY, paste the snippet, run. The recipes lean on three core signal endpoints — see Trending, Narrative, and Alerts for the full envelopes powering each tile and event.

1. Newsroom — catch breaking stories before the wires

Goal: alert the news desk when a topic spikes outside its normal pattern. Tier: Watch trial sufficient for global. See/Know required for cyber/finance/disinfo. Endpoints: GET /v1/topics/{topic}/alerts, optional webhook subscription. See Alerts for the full alert envelope, signal types, IOC schema, and webhook delivery details. A real signal from this pipeline (2026-05-18, 6.67σ above 14-day baseline, validated by our LLM gate):
Multiple credible data breach disclosures (Turkish breach, FoxIT/Foxit software, gaming accounts) surfacing on dark web with fact-checker verification signals genuine cybersecurity incidents being reported and discussed across platforms.
Cost: 1,440 calls/day per topic. Comfortably inside Watch’s 5,000-call monthly budget for one topic; trivial on See’s 250,000 monthly budget across multiple topics. Upgrade path: swap polling for a webhook subscription (See/Know) to get sub-second push delivery into Slack/Teams/PagerDuty without burning RPM.

2. Brand monitoring with watchlists

Goal: track every public mention of your brand, your domains, and your executives — across the whole conversation, not just one platform. Tier: See or Know. Endpoints: POST /v1/watchlists, GET /v1/watchlists/{id}/(trending|entities|platforms|posts|alerts). See Topics and watchlists for the full term-type reference.
Why watchlists beat keyword-only search: the Exorde pipeline already classifies entities and clusters posts by narrative. A watchlist runs the same pipeline filtered to your terms, so you get structured signal — entity leaderboards, platform breakdowns, narrative summaries — not a keyword feed.

3. Threat-intel desk — daily cyber alert digest

Goal: every morning, the analyst sees yesterday’s high-σ cyber events with IOCs extracted, sample posts, and matched cluster context. Tier: See. Endpoints: GET /v1/topics/cyber/alerts, GET /v1/topics/cyber/clusters/{id} for drill-down. Full alert envelope including the IOC schema lives in Alerts.
Sample output, real run from 2026-05-18: Cyber digest, 2026-05-19 [2026-05-18T04:00:30.148Z] σ=6.67 ‘dark web’ Multiple credible data breach disclosures (Turkish breach, FoxIT/Foxit software, gaming accounts) surfacing on dark web with fact-checker verification… cluster: Dark-web breach disclosures, May 2026 Drill-down: for any alert with a matched_cluster.cluster_id, fetch the full cluster context with GET /v1/topics/cyber/clusters/{id} (See tier) — top entities, top domains, time-series, full evidence post list.

4. Disinformation early-warning

Goal: catch coordinated narrative pushes before they reach mainstream amplification — multi-platform, multi-language synchronisation, LLM-validated. Tier: See or Know. Endpoints: GET /v1/topics/disinfo/alerts, GET /v1/topics/disinfo/narratives/history, GET /v1/topics/disinfo/platforms.
Operational tip: combine the disinfo signal with /narratives/history (See tier) to see whether the alert is part of a longer-running narrative pivot or a sudden burst. A campaign that’s been smouldering for two weeks behaves very differently from one that’s a 6-hour burst.

5. Executive dashboard — single-pane situational awareness

Goal: one page that shows, for every curated topic: latest narrative, top 3 trending terms, alert count last 24h, freshness. Tier: See. Endpoints: GET /v1/topics/{t}/(narrative|trending|alerts) × 4 topics. See Trending and Narrative for the full response envelopes powering each tile.
Cost: 12 API calls per refresh (3 endpoints × 4 topics). Refresh every minute = 12 calls/minute, comfortably inside See’s 120 RPM (10% utilisation) and a rounding error against See’s 250,000 monthly quota.

What to build next

Reach out if you have a use case that doesn’t map cleanly onto these — most of our paid contracts started as a “can you do X” email.
Last reviewed: 2026-05-19. API version 1.2.8. All snippets tested against production.