Apify · scraping + community sentiment
Five scraping platforms, wired into one game —
and one of them sells.
Every link a player posts is dereferenced before it reaches another player. Every mention of the game on Instagram, TikTok, YouTube, Reddit, Steam and HN is scored and trended. Every rival studio's patch notes are diffed overnight. The engine that does it is published on the Apify Store as a pay-per-result product.
Live · monetized · Apify Store
ALL-IN-ONE Market Sentiment Marker
The internal sentiment engine, productized. Type a brand and get back one number — a Market Sentiment Index across Instagram, TikTok, YouTube and News, plus benchmarking against the competitors you name.
- Pay-per-result: $1 per 1,000 rows — you pay for rows returned, not for compute.
- One index, four surfaces — the same classifier that grades the game's own community.
- Published from account #1, executed on account #2 — the listing never moves.
The Store listing is the reason account #1 is kept alive after running out of credit: it owns the publication. Execution moved to Apify 2 through the token resolver, with zero pipeline changes.
{ "brand": "<any brand>", "index": +37, // −100 … +100 "surfaces": ["instagram", "tiktok", "youtube", "news"], "benchmark": ["<competitor>", "…"], "pricing": "$1 / 1k results" }
Shape of the Actor's output. Index value is illustrative.
Business use cases · gathered from all apps
Compiled from the actual integrations in this deployment — the chat pipeline, the
server-node/scripts jobs and the systemd timers — not from vendor marketing.
What the status labels mean
- live
- On the hot path or on a timer today.
- gated
- Built and fed with real data, but off by default behind an env flag.
- dormant
- Ready, and spends nothing until it is pointed at a target.
The full cross-app business-case set is repeated on every app tab of the console (that app's rows first, highlighted), so any single tab tells the whole story. This page is that register, unrolled.
The day, on a timer
Three unattended sweeps before breakfast, one continuous guardrail, and one signal loop that is deliberately switched off.
Where this lives
The register above is one tab of an internal, read-only admin console that also fronts an agent fleet. Access is authenticated and read-only; this public page is a static extract.
Agent fleet
Connector tabs
Ground rules
- Keys stay server-side. Every paid key is proxied; none is ever shipped to a client.
- Read-only. The console only ever GETs against vendor APIs.
- Fail-open. The chat guardrail never stalls chat, even when a scan fails.
- PII-excluded. The DB→dataset mirror redacts credentials and ships analytics-only columns.
How to read this page
The words are not marketing copy
Every use-case description here is lifted verbatim from the console's own business-case register, which was written against the integrations as they are actually deployed — timers, env flags, table names and all.
Nothing here claims to be more than it is
Eleven of the fourteen entries are live. One is gated and has zero effect on live matches by default. Two are dormant and spend nothing. Those labels are kept on the page precisely because they are unflattering.
The status strip is a snapshot
The connector pills at the top of this page were captured on 6 August 2026 at 01:06. This site is static and does not poll any vendor — it will not tell you whether ClickHouse is reachable right now.
Two accounts, on purpose
Account #1 owns the published Store listing and is out of credit. Account #2 runs everything. A token resolver picks the active one, so continuity cost nothing but a config preference.